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 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 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 Gibson wrote: >>> >>>> 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 endpoints (2) >>>> >>>> And I got this error on the new node: >>>> >>>> Bootstraping to existing token 113427455640312821154458202477256070484 >>>> is not allowed (decommission/removetoken the old node first). >>>> >>>> - >>>> >>>> Do I really need to do the token - 1 manual selection for this? >>>> >>>> Thanks >>> >>> > >
