cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jens Rantil <jens.ran...@tink.se>
Subject Re: Is to ok restart DECOMMISION
Date Fri, 16 Sep 2016 07:35:59 GMT
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 <markrose@markrose.ca> 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 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 died on anything. If
> so, the decommission process will never finish. If not, let it
> continue. Of particular note is that by default transferring large
> sstables will timeout. You can fix that by adjusting
> streaming_socket_timeout_in_ms to a sufficiently large value (I set it
> to a day).
>
> -Mark
>
> On Thu, Sep 15, 2016 at 9:28 AM, laxmikanth sadula
> <laxmikanth524@gmail.com> wrote:
> > I started decommssioned a node in our cassandra cluster.
> > But its taking too long time (more than 12 hrs) , so I would like to
> > restart(stop/kill the node & restart 'node decommission' again)..
> >
> > Does killing node/stopping decommission and restarting decommission will
> > cause any issues to cluster?
> >
> > Using c*-2.0.17 , 2 Data centers, each DC with 3 groups each , each group
> > with 3 nodes with RF-3
> >
> > --
> > Thanks...!
>
-- 

Jens Rantil
Backend Developer @ Tink

Tink AB, Wallingatan 5, 111 60 Stockholm, Sweden
For urgent matters you can reach me at +46-708-84 18 32.

Mime
View raw message