Re: Replacing dead node and cassandra.replace_address

2015-09-08 Thread Vasileios Vlachos
I think you should be able to see the streaming process by running nodetool netstats. I also think system.log displays similar information about stemming/when stemming is finished. Shouldn't the state of the node change to UP when bootstrap is completed as well? People, correct me if I'm wrong her

Re: Replacing dead node and cassandra.replace_address

2015-09-08 Thread Maciek Sakrejda
On Tue, Sep 8, 2015 at 11:14 AM, sai krishnam raju potturi < pskraj...@gmail.com> wrote: > Once the new node is bootstrapped, you could remove replacement_address > from the env.sh file > Thanks, but how do I know when bootstrapping is completed?

Re: Replacing dead node and cassandra.replace_address

2015-09-08 Thread sai krishnam raju potturi
Once the new node is bootstrapped, you could remove replacement_address from the env.sh file On Tue, Sep 8, 2015, 13:27 Maciek Sakrejda wrote: > According to the docs [1], when replacing a Cassandra node, I should start > the replacement with cassandra.replace_address specified. Does that just >

Replacing dead node and cassandra.replace_address

2015-09-08 Thread Maciek Sakrejda
According to the docs [1], when replacing a Cassandra node, I should start the replacement with cassandra.replace_address specified. Does that just become part of the replacement node's startup configuration? Can I (or do I have to) stop specifying it at some point? Does this affect subsequent node