Hi Morten, it might be a bug, which C* version are you using? To guarantee
consistency, it's recommended to run repair on all nodes after removeNode
(for NetworkTopologyStrategy, it could be all nodes in that specific
datacenter).
On Thu, Jul 4, 2019 at 8:30 AM Alain RODRIGUEZ wrote:
> Hello,
>
Hello,
Just for one node, and if you have a strong consistency 'Read CL + Write CL
> RF', you can:
- force the node out with 'nodetool removenode force' if it's still around
- run a repair (just on that node, but full repair).
OR
- force the node out with 'nodetool removenode force' if it's still
Hi,
We had a hardware issue with one node in a Cassandra cluster and had to use the
"nodetool removenode UUID" command from a different node. This seems to be
running fine, but one node was restarted after the "nodetool removenode"
command was run, and now it seems all streams going from that
