Hi Jeff, thanks for getting back to me. I have gone through the output of nodetool netstats, and it seems all the streams are 100% completed as per the output. What else do you think is going wrong?
-Mir On Thu, Apr 21, 2016 at 10:27 AM, Jeff Jirsa <jeff.ji...@crowdstrike.com> wrote: > The keyspace with RF=1 may lose data, but isn’t blocking the replacement. > > The most likely cause of the delay is hung streaming. Run `nodetool > netstats` on the joining (replacement) node. Do the byte counters change? > If not, streaming is hung, and you’ll likely need to restart the process. > If so, use the byte counters to calculate streaming percentage complete and > extrapolate. > > > > From: Mir Tanvir Hossain > Reply-To: "user@cassandra.apache.org" > Date: Thursday, April 21, 2016 at 10:02 AM > To: "user@cassandra.apache.org" > Subject: Problem Replacing a Dead Node > > Hi, I am trying to replace a dead node with by following > https://docs.datastax.com/en/cassandra/2.0/cassandra/operations/ops_replace_node_t.html. > It's been 3 full days since the replacement node started, and the node is > still not showing up as part of the cluster on OpsCenter. I was wondering > whether the delay is due to the fact that I have a test keyspace with > replication factor of one? If I delete that keyspace, would the new node > successfully replace the dead node? Any general insight will be hugely > appreciated. > > Thanks, > Mir > > >
