Hi Eric, Reip was deprecated because it had a lot of issues. For reip to work as expected you need to take the entire cluster down and run the riak-admin reip command on all nodes to reassign the node name in all the ring files. This is obviously not what users want.
The 'riak-admin cluster replace' command was added for this reason. The procedure to replace one node with another is as follows: 1. Turn on new node, start riak 2. riak-admin cluster join <node already in cluster> 3. riak-admin cluster replace <old node> <new node> 4. riak-admin cluster plan 5. Confirm pending changes are as expected 6. riak-admin cluster commit 7. The old node will shut down once it has transferred all data to the new node Aside: The rate of transfer can be tuned via 'riak-admin transfer-limit' Thanks! -- Brian Sparrow Developer Advocate Basho Technologies Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On Wednesday, November 28, 2012 at 11:15 AM, Eric Abbott wrote: > the riak-admin reip command would appear to allow one to shut down a server, > copy all data to a new server, and run riak-admin reip to bring that nodes > data back into the cluster on a new server. > > Does that work I just described actually work, and if so, is that > functionality supported by riak-admin cluster replace? > > Thanks, > > Eric > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com (mailto:riak-users@lists.basho.com) > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > >
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
