Re: Lightweight transaction in Multi DC

Thanks for your reply. I understand that LOCAL_SERIAL is for within a DC , will setting up SERIAL not slow down the operation? And should I set SERIAL for both read and write phase or just Read phase? This is becoming a big problem for us. It happens for a small percentage of data set but it

Re: Lightweight transaction in Multi DC

LOCAL_SERIAL is dc level, SERIAL checks for complete cluster level. On Fri, Sep 8, 2017 at 2:33 PM, Charulata Sharma (charshar) < chars...@cisco.com> wrote: > Yes …it is with LOCAL_SERIAL. Should I be using SERIAL ? > > > > Thanks, > > Charu > > > > *From: *DuyHai Doan >

Re: How to do cassandra routine maintenance

Hi, You should read about repair maintenance:  http://cassandra.apache.org/doc/latest/operating/repair.htmlConsider installing and running C* reaper to do so: http://cassandra-reaper.io/STCS doesn't work well with TTL. I saw you have done some tuning, hard to say if it's OK without knowing the

Re: Cassandra 3.11 is compacting forever

Hi, It might be useful to enable compaction logging with log_all subproperties. Best, Romain Le vendredi 8 septembre 2017 à 00:15:19 UTC+2, kurt greaves a écrit : Might be worth turning on debug logging for that node and when the compaction kicks off and CPU

Re: Lightweight transaction in Multi DC

Yes …it is with LOCAL_SERIAL. Should I be using SERIAL ? Thanks, Charu From: DuyHai Doan Reply-To: "user@cassandra.apache.org" Date: Friday, September 8, 2017 at 12:30 PM To: "user@cassandra.apache.org" Subject: Re:

Re: Lightweight transaction in Multi DC

Are you using CAS with SERIAL consistency level for your multi-DC setup ? On Fri, Sep 8, 2017 at 9:27 PM, Charulata Sharma (charshar) < chars...@cisco.com> wrote: > Hi, > > We are facing a serious issue with CAS in a multi DC setup and I > wanted to get some input on it from the forum. > >

Lightweight transaction in Multi DC

Hi, We are facing a serious issue with CAS in a multi DC setup and I wanted to get some input on it from the forum. We have a Column family which stores counts for the number of events our application receives. When the counts reach a certain threshold, there is another process which

Re: Limit on number of connections to Cassandra

Hello, If I'm understanding the question correctly, as of C* 2.0.15 / 2.1.5 via CASSANDRA-8086 you can limit the maximum number of connections allowed to a C* node via native_transport_max_concurrent_connections

Limit on number of connections to Cassandra

Hi Is there any limit on number of client connections to Cassandra just like MySQL etc., ? If YES, what is that & how can we set that? If NO , how will get to know that node has reached it's capacity serving client requests/over loaded? Using C*-2.1.17 , datastax java driver Thanks

Re: New Column addition and Locking

CASSANDRA-13004 -- Jeff Jirsa > On Sep 8, 2017, at 7:33 AM, Deepak Panda wrote: > > Many Thanks Jeff for the answer and the relevant details. Can you > please share the bug#? > > Are there any opensource tools available for Cassandra which manage > schema changes for

Re: New Column addition and Locking

Many Thanks Jeff for the answer and the relevant details. Can you please share the bug#? Are there any opensource tools available for Cassandra which manage schema changes for Cassandra? On Fri, Sep 8, 2017 at 7:57 PM, Jeff Jirsa wrote: > There is no lock and it doesn't block

Re: New Column addition and Locking

There is no lock and it doesn't block existing reads or writes You're already on 3.11, but as a reminder for others there's a bug in 3.0 versions between (3.0.0 and 3.0.14) and (3.0 and 3.11.0) that can cause corruption when you add columns. It's fixed in both 3.11.0 and 3.0.14, so if you need

New Column addition and Locking

Hi, For Cassandra 3.11, when we add a new column is added to an existing table having huge number of rows and huge data manipulation going on will there be any issues? Will the operations blocked till the column is added? Is the table locked during column addition? If yes, what type of lock?

Re: Stop writes to a cassandra node for maintenance purpose & enable them after some time

Keep in mind that hints will accumulate for this node across the cluster for *max_hint_window_in_ms* (default: 3hrs) On Fri, Sep 8, 2017 at 8:20 AM, Jeff Jirsa wrote: > nodetool disablebinary (will make the node down for native cql clients, > stopping client apps from writing

Re: Stop writes to a cassandra node for maintenance purpose & enable them after some time

nodetool disablebinary (will make the node down for native cql clients, stopping client apps from writing directly over tcp/9042) nodetool disablethrift (will make the node down for thrift clients, stopping client apps from writing directly over tcp/9160) nodetool disablegossip (will make the node