Re: [Cassandra 3.0.9] Cannot allocate memory

2017-03-22 Thread Abhishek Verma
Just a shot in the dark, but what is your setting of vm.max_map_count in /etc/sysctl.conf ? It is recommended to set it to: vm.max_map_count = 1048575 Source: https://docs.datastax.com/en/landing_page/doc/landing_page/recommendedSettingsLinux.html We saw a similar problem in the past where mmap

Re: Pluggable throttling of read and write queries

2017-02-22 Thread Abhishek Verma
where cost is no issue, the >> additional isolation and workload tailoring is still highly valuable. >> >> On Wed, Feb 22, 2017 at 12:01 PM Edward Capriolo > <mailto:edlinuxg...@gmail.com>> wrote: >> >> >> >> On Wed, Feb 22, 2017 at 1:20 PM,

Re: Pluggable throttling of read and write queries

2017-02-22 Thread Abhishek Verma
o meet those uses >>> cases. >>> >> There have been several instances where we have moved customers out of the shared cluster to their own dedicated clusters because they outgrew our limitations. But I don't think it makes sense to move all the small use cases into their separa

Pluggable throttling of read and write queries

2017-02-17 Thread Abhishek Verma
Cassandra is being used on a large scale at Uber. We usually create dedicated clusters for each of our internal use cases, however that is difficult to scale and manage. We are investigating the approach of using a single shared cluster with 100s of nodes and handle 10s to 100s of different use ca

Re: Bootstrapping data from Cassandra 2.2.5 datacenter to 3.0.8 datacenter fails because of streaming errors

2016-10-10 Thread Abhishek Verma
o be schema mismatches temporarily >> while you have a mixed version cluster – this isn’t necessarily a huge >> problem, but do try to get to 3.0.8 as quickly as possible once you start, >> and if you can avoid administrative tasks (such as those that will change >> the s

Bootstrapping data from Cassandra 2.2.5 datacenter to 3.0.8 datacenter fails because of streaming errors

2016-10-10 Thread Abhishek Verma
Hi Cassandra users, We are trying to upgrade our Cassandra version from 2.2.5 to 3.0.8 (running on Mesos, but that's besides the point). We have two datacenters, so in order to preserve our data, we are trying to upgrade one datacenter at a time. Initially both DCs (dc1 and dc2) are running 2.2.5