jbellis talked about incremental repair, which is great, but as I understood,
repair was also somewhat responsible for detecting and repairing bitrot on
long-lived sstables.
If repair doesn't do it, what will?
Thanks,
John...
NOTICE: This email message is for the sole use of the intended
If you only run incremental repairs, does that mean that bitrot will go
undetected for already repaired sstables?
If so, is there any other process that will detect bitrot for all the repaired
sstables other than full repair (or an unfortunate user)?
John...
NOTICE: This email message is
I have a 24 node cluster, with vnodes set to 256.
'nodetool status ' looks like this for our keyspace:
UN 588.23 GB 256 11.0%
0c8708a7-b962-4fc9-996c-617da642d9ee 1a
UN 601.33 GB 256 11.3%
5ef60730-0b01-4a8b-a578-d828cdf78a1f 1b
UN 613.02 GB
Is there a JMX property somewhere that I could monitor to see how old the
oldest row cache item is?
I want to see how much churn there is.
Thanks in advance,
John...
Here is a tool I worked on to figure out which node to decommission that will
leave you with the most even token balance afterwards.
https://github.com/jdsumsion/vnode-decommission-calculator
Feel free to use or enhance as you desire.
John...
I've seen something similar if there is a node still referring to that IP as a
seed node in cassandra.yaml. You might want to check that.
From: Vincent Rischmann
Sent: Wednesday, August 28, 2019 10:10 AM
To: user@cassandra.apache.org
Subject: Re: gossipinfo
Pat,
You might find this post useful in tuning G1 for Cassandra:
*
http://deliberate-thinking.blogspot.com/2019/05/tuning-g1-gc-for-cassandra.html
This assumes a machine with 60-120G of RAM -- and your use case may be
different than the clusters I've tuned, so take each step with care.
