Re: restarting node makes cpu load of the entire cluster to raise

Hi guys, just for the record, in case someone has this issue in the future, it is a bug, fixed in 1.2.12. I recommend anyone in this version to upgrade cluster before getting totally stuck (by adding new machines / DC / altering keyspaces / ...), well anything using gossip actually. We are going t

Counters: consistency, atomic batch

Hi all, I am using Cassandra 2.0.x. and Astyanax 1.56.x (2.0.1 shows the same results) driver via Thrift protocol. Questions about counters: 1. Consistency. Consider simplest case when we update value of single counter. 1.1. Is there any difference between updating counter with ONE or QUORU

Cassandra JBOD disk configuration

Hi, Let's imagine that I have one keyspace with one big table configured with size tiered compaction strategy and nothing else. The disk configuration would to have 10x 500GB disks, each mounted to separate directory. Each directory would then be configured as a separate entry in cassandra.yaml.

Moving a server from one DC to another

I have a situation where I need to move a server from one DC to another DC. I am using the ProperFileSnitch and my cassandra-topology.properties looks like this. Server150=CLV:RAC1 Server151=CLV:RAC1 Server152=CLV:RAC1 Server153=DPT:RAC1 Server154=DPT:RAC1 Server155=DPT:RAC1 Server156=DPT:RAC1 S

Pending tasks are not being processed.

Hi all, Yesterday I put a lot of blobs into Cassandra and it created many, probably compaction, pending tasks (few hundreds according to Ops Center). On all nodes all pending tasks were eventually processed, but on one problematic, I see no related activity. Problematic node seems to be responsive

Re: Pending tasks are not being processed.

On Thu, Sep 4, 2014 at 8:09 AM, Pavel Kogan wrote: > Yesterday I put a lot of blobs into Cassandra and it created many, > probably compaction, pending tasks (few hundreds according to Ops Center). > On all nodes all pending tasks were eventually processed, but on one > problematic, I see no relat

Re: Pending tasks are not being processed.

Should I experience any problems even if split versions vary only by minor digit? After another restart of node, it seems that the problem was solved somehow. Regards, Pavel On Thu, Sep 4, 2014 at 1:59 PM, Robert Coli wrote: > On Thu, Sep 4, 2014 at 8:09 AM, Pavel Kogan > wrote: > >> Yeste

Re: Pending tasks are not being processed.

On Thu, Sep 4, 2014 at 11:54 AM, Pavel Kogan wrote: > Should I experience any problems even if split versions vary only by minor > digit? > My statement states what it states, no more and no less. It is Not Supported to run with split minor version, single digit increment or not, for longer than

Re: Counters: consistency, atomic batch

Counters are way more complicated than what you're illustrating. Datastax did a good blog post on this: http://www.datastax.com/dev/blog/whats-new-in-cassandra-2-1-a-better-implementation-of-counters On Thu, Sep 4, 2014 at 6:34 AM, Eugene Voytitsky wrote: > Hi all, > > I am using Cassandra 2.

Question about EC2 and SSDs

Hi all, We are migrating a small cluster on AWS from instances based on spinning disks (using instance store) to SSD-backed instances and we're trying to pick the proper instance type. Some of the recommendations for spinning disks say to use different drives for log vs data partitions to avoid is

Re: Question about EC2 and SSDs

With SSD one drive should be sufficient for both data and commitLogs. Rahul Neelakantan > On Sep 4, 2014, at 8:05 PM, Steve Robenalt wrote: > > Hi all, > > We are migrating a small cluster on AWS from instances based on spinning > disks (using instance store) to SSD-backed instances and we're

Re: Question about EC2 and SSDs

On Thu, Sep 4, 2014 at 5:05 PM, Steve Robenalt wrote: > We are migrating a small cluster on AWS from instances based on spinning > disks (using instance store) to SSD-backed instances and we're trying to > pick the proper instance type. Some of the recommendations for spinning > disks say to use

Re: Question about EC2 and SSDs

Thanks Rahul! That was my inclination, but I don't want to take things like that for granted. Anybody have a dissenting view? Steve On Thu, Sep 4, 2014 at 5:14 PM, Rahul Neelakantan wrote: > With SSD one drive should be sufficient for both data and commitLogs. > > Rahul Neelakantan > > > On S

Re: Question about EC2 and SSDs

Thanks Robert! I am assuming that you meant that it's possible with a single SSD, right? On Thu, Sep 4, 2014 at 5:42 PM, Robert Coli wrote: > On Thu, Sep 4, 2014 at 5:05 PM, Steve Robenalt > wrote: > >> We are migrating a small cluster on AWS from instances based on spinning >> disks (using in

Re: Question about EC2 and SSDs

On Thu, Sep 4, 2014 at 5:44 PM, Steve Robenalt wrote: > Thanks Robert! I am assuming that you meant that it's possible with a > single SSD, right? > Yes, no matter how many SSDs you have you are unlikely to be able to convince one of them to physically seek a drive head across its plater, becaus

Re: Question about EC2 and SSDs

On 5 Sep 2014, at 10:05 am, Steve Robenalt wrote: > We are migrating a small cluster on AWS from instances based on spinning > disks (using instance store) to SSD-backed instances and we're trying to pick > the proper instance type. Some of the recommendations for spinning disks say > to use d

Re: Question about EC2 and SSDs

Yes, I am aware there are no heads on an SSD. I also have seen plenty of examples where compatibility issues force awkward engineering tradeoffs, even as technology advances so I am jaded enough to be wary of making assumptions, which is why I asked the question. Steve On Sep 4, 2014 5:50 PM, "Rob