Not marking node down due to local pause

I have a small, two-node cluster running Cassandra 2.2.1. I am seeing a lot of these messages in both logs: WARN 07:23:16 Not marking nodes down due to local pause of 7219277694 > 50 I am fairly certain that they are not due to GC. I am not seeing a whole of GC being logged and nothing o

Re: Best approach to prepare to shutdown a cassandra node

Does, nodetool stopdaemon, implicitly drain too? or we should invoke drain and then stopdaemon? On Mon, Oct 16, 2017 at 4:54 AM, Simon Fontana Oscarsson < simon.fontana.oscars...@ericsson.com> wrote: > Looking at the code in trunk, the stopdemon command invokes the > CassandraDaemon.stop() functi

Re: split one DC from a cluster

Easiest way is to separate them via firewall/network partition so the DC's can't talk to each other, ensure each DC sees the other DC as DOWN, then remove the other DC from replication, then remove all the nodes in the opposite DC using removenode.​

split one DC from a cluster

Hi, We want to split one DC from a cluster and make this DC a new cluster(rename this DC to a new cluster name). Could you please advise? Thanks, Peng Xiao

Re: 3.0 is slower than 2.2 ?

Thanks Jeff, Non-conditional write performance of 3.0.15 is also lower than 2.2.10. And, I've tried 3.11.1. It's faster than 2.2.10 and 3.0.15. - INSERT | Concurrency |2.2.10 [op/s]|3.0.15 [op/s]|3.11.1 [op/s]| | 1 | 303 | 263 | 322 | | 2 | 526 | 454 | 571 | | 4 | 784 | 666 | 833 | | 8 | 1066 |