unsubscribe

unsubscribe

Upgrade from 2.1.11 to 3.0.5 leads to unstable nodes

Hi, I am experiencing some weird behaviors after upgrading 2 nodes (out of 13) to C* 3.0.5 (from 2.1.11). Basically, after restarting a second time, there is a small chance that the node will die without outputting anything to the logs (not even dmesg). This happened on both nodes I upgraded.

Re: CAS operation does not return value on failure

Hi Jack, I thought that it is Cassandra that fills the value on CAS failures. So the question if it is to be expected to have wasApplied()==false and not have any value in the ResultSet should belong here. So my question for this mailing list would be: Is it correct behaviour that C* returns

Re: Read data from specific node in cassandra

This doesn’t actually guarantee the behavior you think it does. There’s no actual way to guarantee this behavior in Cassandra, as far as I can tell. A long time ago there was a ticket for a “coordinator only” consistency level, which is nearly trivial to implement, but the use case is so narrow

Re: Read data from specific node in cassandra

Hi, Can you check LoadBalancing Policy -> whiteList ? jasonstack Varun Barala 于2016年5月5日周四 下午5:40写道： > Hi Siddharth Verma, > > You can define consistency level LOCAL_ONE. > > and you can applyh consistency level during statement creation. > > like this ->

Re: Read data from specific node in cassandra

Hi Siddharth Verma, You can define consistency level LOCAL_ONE. and you can applyh consistency level during statement creation. like this -> statement.setConsistencyLevel(ConsistencyLevel.LOCAL_ONE); On Thu, May 5, 2016 at 3:55 PM, Siddharth Verma < verma.siddha...@snapdeal.com> wrote: > Hi,

Read data from specific node in cassandra

Hi, We have a 3 node cluster in DC1, where replication factor of keyspace is 3. How can i read data only from one particular node in java driver? Thanks, Siddharth Verma