Performance impact of wide rows on read heavy workload

Hi, We are trying to evaluate read performance impact of having a wide row by pushing a partition out into clustering column. From all the information I could gather[1] [2]

Re: UNSUBSCRIBE

Thanks & Regards, Chandana.T From: Raman Kannan Sent: Friday, July 22, 2016 6:20:08 AM To: user@cassandra.apache.org Subject: UNSUBSCRIBE ** This mail has been sent from an external source ** The information contained in this

UNSUBSCRIBE

Re: Exclude a host from the repair process

Hi @Alain Rodriguez.what I mean is repiar will ignore all the replica data that stored in down node.and continue to repair other data. once the down node up,then repair can work on the replica data belong to the down node. run repair always a daily work with auto script.we dont need to exclude

Re: Cassandra stable version for production

Yes, we have been running 3.0.x for a while and we consider it mostly stable now. Though, we did not have to bootstrap new nodes / new DCs since running 3.0.x so I cannot speak about that part. In addition, DSE 5 is now running off 3.0.x which will definitely bring a lot of bug fixes from

Re: Re : Recommended procedure for enabling SSL on a live production cluster

Thank you Nate. We are currently on 2.0.14. So the only option we are left with is the upgrade to 2.1.12. So for the earlier versions there is no way to enable SSL once the cluster is in production. Thanks again Nate. Thanks Sai On Wed, Jul 20, 2016, 17:26 Nate McCall

multi datacenter improvement

Hi All, I am thinking about the issue of cassandra multi datacenter. open a ticket to track this.welcome to your point. https://issues.apache.org/jira/browse/CASSANDRA-12257 *Environment* active-active cassandra datacenter. set write consistency level=local_quorum to get a high resquest response.

Re: Repair and LCS tables

> What Cassandra version are you using? 2.1.14 > > There a lot of recent and ongoing work around LCS. Maybe one of these tickets > will be of interest to you: > > https://issues.apache.org/jira/browse/CASSANDRA-10979 > >

Re: Exclude a host from the repair process

@Alain now we agree with on this point "the repair continuing for ranges not involving the dead node" and we agree with that it will fail for ranges involve the down node. actually i dont think this is a good idea of “those ranges including the dead node could be repaired between the 2 other

Re: Exclude a host from the repair process

> > what I mean is repiar will ignore all the replica data that stored in down > node.and continue to repair other data. > once the down node up,then repair can work on the replica data belong to > the down node. > That's what I understood the first time, but thanks for trying to clarify :-). I