Just wanted to update and say the move was completed without any
issues in v 0.7.8. Thanks for all the help everyone.
On Mon, Sep 12, 2011 at 4:31 PM, Jeremy Hanna
jeremy.hanna1...@gmail.com wrote:
So to move data from node with token 0, the new node needs to have
initial token set to
Version=0.7.8
I have a 3 node cluster with RF=3, how would I move data from a live
node to a replacement node?
I tried an autobootstrap + decomission, but I got this error on the live node:
Exception in thread main java.lang.IllegalStateException:
replication factor (3) exceeds number of
Yeah - I would bootstrap at initial_token of -1 the current one. Then once
that has bootstrapped, then decommission the old one. Avoid trying to use
removetoken on anything before 0.8.3. Use decommission if you can if you're
dealing with a live node.
On Sep 12, 2011, at 10:42 AM, Kyle
What could you do if the initial_token is 0?
On Mon, Sep 12, 2011 at 1:09 PM, Jeremy Hanna
jeremy.hanna1...@gmail.com wrote:
Yeah - I would bootstrap at initial_token of -1 the current one. Then once
that has bootstrapped, then decommission the old one. Avoid trying to use
removetoken on
The ring wraps around, so the value before 0 is the max possible token. I
believe that it is 2**127 -1 .
- Original Message -
From: Kyle Gibson kyle.gib...@frozenonline.com
To: user@cassandra.apache.org
Sent: Monday, September 12, 2011 3:30:20 PM
Subject: Re: Replace Live Node
What
I believe you'd need 2^127 - 1, which is 170141183460469231731687303715884105727
On Sep 12, 2011, at 2:30 PM, Kyle Gibson wrote:
What could you do if the initial_token is 0?
On Mon, Sep 12, 2011 at 1:09 PM, Jeremy Hanna
jeremy.hanna1...@gmail.com wrote:
Yeah - I would bootstrap at
So to move data from node with token 0, the new node needs to have
initial token set to 170141183460469231731687303715884105727 ?
Another idea: could I move token to 1, and then use token 0 on the new node?
On Mon, Sep 12, 2011 at 3:38 PM, Jeremy Hanna
jeremy.hanna1...@gmail.com wrote:
I
So to move data from node with token 0, the new node needs to have
initial token set to 170141183460469231731687303715884105727 ?
I would do this route.
Another idea: could I move token to 1, and then use token 0 on the new node?
nodetool move prior to 0.8 is a very heavy operation.
