Cassandra read requests not getting timeout

Hi Community, I am using Cassanadra 3.0.13 . 5 node cluster simple topology. Following are the timeout parameters in yaml file: # grep timeout /etc/cassandra/conf/cassandra.yaml cas_contention_timeout_in_ms: 1000 counter_write_request_timeout_in_ms: 5000 cross_node_timeout: false

Cassandra repair in different version

Hi , i have 5 node cassandra cluster. 3 nodes are in 3.0.13 version and 2 nodes are in 3.0.6. Is it safe to do a node repair on the cluster?? Regards, Renoy

Re: Too many Cassandra threads waiting!!!

gmail.com%3E > > On Wed, Aug 1, 2018 at 5:38 PM, Elliott Sims > wrote: > >> You might have more luck trying to analyze at the Java level, either via >> a (Java) stack dump and the "ttop" tool from Swiss Java Knife, or Cassandra >> tools like "nodetool tps

Too many Cassandra threads waiting!!!

Hi, i'm having a 5 node cluster with cassandra 3.0.13. i could see the cassandra process has too many threads. *# pstree -p `pgrep java` | wc -l* *453* And almost all of those threads are in *sleeping* state and wait at *# cat /proc/166022/task/1698913/wchan* *futex_wait_queue_me* Some more

Re: Cassandra + NUMA integration

40 9018.98 Env, RHEL7.3 3.10.0-514.2.2.el7.x86_64 cassandra30-3.0.6-1.noarch Awaiting for comments Thanks On Thu, Mar 16, 2017 at 5:07 PM, nokia ceph <nokiacephus...@gmail.com> wrote: > Hello, > > Recently we tried top integrate cassandra with NUMA > > == >

Cassandra + NUMA integration

Hello, Recently we tried top integrate cassandra with NUMA == commented out the numactl --interleave in bin/cassandra and add -XX:+UseNUMA to cassandra-env.sh. == But after inplementing, we saw HEAP and STACK values were changed to null. #/usr/bin/numactl --cpunodebind=1 -- /usr/sbin/cassandra