On Mon, Dec 17, 2018 at 11:44 AM Riccardo Ferrari
wrote:
> I am having "the same" issue.
> One of my nodes seems to have some hardware struggle, out of 6 nodes (same
> instance size) this one is likely to be makred down, it consntantly
> compacting, high system load, it's just a big pain.
>
> My
> Cluster?
> Using Apache Cassandra 3.11.2
>
> Sent using Zoho Mail <https://www.zoho.com/mail/>
>
>
> Forwarded message
> From : onmstester onmstester
> To : "user"
> Date : Wed, 05 Dec 2018 09:00:34 +0330
> Subject : Fwd:
15 +0330 Subject : Re: How to gracefully decommission a highly loaded
node? Forwarded message
- To
unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional
commands, e-mail: user-h...@cassand
ommissioning process, but the
node became UN after restart. Sent using Zoho Mail Forwarded
message From : Simon Fontana Oscarsson
To :
"user@cassandra.apache.org" Date : Tue, 04 Dec 2018
15:20:15 +0330 Subject : Re: How to gracefully decommission a highly loaded
node?
Hi,
If it already uses 100 % CPU I have a hard time seeing it being able to
do a decomission while serving requests. If you have a lot of free
space I would first try nodetool disableautocompaction. If you don't
see any progress in nodetool netstats you can also disablebinary,
disablethrift and
One node suddenly uses 100% CPU, i suspect hardware problems and do not have
time to trace that, so decided to just remove the node from the cluster, but
although the node state changed to UL, but no sign of Leaving: the node is
still compacting and flushing memtables, writing mutations and CPU
