Looking at the code in trunk, the stopdemon command invokes the
CassandraDaemon.stop() function which does a graceful shutdown by
stopping jmxServer and drains the node by the shutdown hook.
On 10/20/17, Simon Fontana Oscarsson
wrote:
> Yes, drain will
I believe that’s just referencing a counter implementation detail. If I
remember correctly, there was a fairly large improvement of the implementation
of counters in 2.1, and the assignment of the id would basically be a format
migration.
> On Oct 20, 2017, at 9:57 AM, Paul Pollack
Yes, drain will always be run when Cassandra exits normally.
On 2017-10-20 00:57, Varun Gupta wrote:
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
Thanks Kurt,we may will still use snapshot and sstableloader to split this
schema to another cluster.
-- 原始邮件 --
发件人: "kurt";;
发送时间: 2017年10月19日(星期四) 晚上6:11
收件人: "User";
主题: Re: split one DC from a cluster
Hi John,
the other main source of STW pause in the JVM is the safepoint mechanism :
http://blog.ragozin.info/2012/10/safepoints-in-hotspot-jvm.html
If you turn on full GC logging in your cassandra-env.sh file, you will find
lines like this :
2017-10-09T20:13:42.462+: 4.890: Total time for
Hello,
We have cassandra cluster in 3 regions with version 2.1.13, and all of a
sudden we started seeing lot of hints accumulating on the nodes. We are
pretty sure there is no issue with the network between the regions and all
the nodes are up and running all the time.
Is there any other reason
Hi,
I was reading the doc page for nodetool cleanup
https://docs.datastax.com/en/cassandra/2.1/cassandra/tools/toolsCleanup.html
because I was planning to run it after replacing a node in my counter
cluster and the sentence "Cassandra assigns a new counter ID to the node"
gave me pause. I can't