Also have a look at `nodetool netstats` to check if streaming is
progressing or is halted.
Cheers,
Jens
On Fri, Sep 16, 2016 at 3:18 AM Mark Rose wrote:
> I've done that several times. Kill the process, restart it, let it
> sync, decommission.
>
> You'll need enough space on the receiving nodes
I've done that several times. Kill the process, restart it, let it
sync, decommission.
You'll need enough space on the receiving nodes for the full set of
data, on top of the other data that was already sent earlier, plus
room to cleanup/compact it.
Before you kill, check system.log to see if it
hi Laxmi;
what's the size of data per node? If the data is really huge, then let
the decommission process continue. Else; stop the cassandra process on the
decommissioning node, and from another node in the datacenter, do a
"nodetool removenode host-id". This might speed up the decommissioning
pr
As far as I know restarting decommission shouldn't cause any problem to
your cluster, but please note that decommission is not resumable in your
Cassandra version (Resumable support will be introduced in 3.10), thus by
restarting it you will restart the whole process.
On Thu, Sep 15, 2016, 3:29 PM
