Mike, I'm not sure how much the wiki's explanation contributed to your understanding of "leave" but it was out of date, so I just updated it (along with the explanation of "force_remove").
http://wiki.basho.com/Command-Line-Tools---riak-admin.html Sorry about that. Mark On Mon, Apr 23, 2012 at 6:53 PM, Joseph Blomstedt <[email protected]> wrote: > Kyle is correct. > > "riak-admin leave" ensures that all replicas are handed off to other > nodes before the leaving node exits the cluster. This has been the > behavior since Riak 1.0 (released last September). > > "riak-admin force-remove" is the command which immediately removes a > node from the cluster without ensuring handoff of its replicas. This > is a dangerous command, and is designed to only be used in cases were > the normal, safe leave behavior cannot be used -- eg. when the node > you are removing had a major hardware failure and is unrecoverable. > Using "force-remove" will result in a loss of all replicas living on > the removed node, which will need to be recovered through other means > -- such as read repair. > > The standard leave command is an exact opposite of join. Just like a > join, during a leave, you can inspect the current/pending ring state > using "riak-admin member_status" as well as see the list of pending > transfers using "riak-admin ring_status". > > Regards, > Joe > > On Mon, Apr 23, 2012 at 6:26 PM, Kyle Kingsbury <[email protected]> wrote: > > On 04/23/2012 06:23 PM, Michael Radford wrote: > >> > >> Can someone from Basho clarify? > >> > >> I understood "handoff" to mean just that it was handing off > >> *responsibility* for a vnode to another node, and not proactively > >> creating additional replicas of the data. This information just came > >> from our technical contact at Basho on 4/18, so I would assume it's up > >> to date. But I would be happy to learn that riak-admin leave now does > >> the right thing. > > > > > > Not that I work for basho, but I can absolutely confirm that riak-admin > > leave (>= 1.1, don't recall 1.0) does involve taking data the local node > is > > responsible for and giving it to the remote node. You can watch the file > > sizes on hosts or network traffic to confirm. > > > > > > --Kyle > > > > _______________________________________________ > > riak-users mailing list > > [email protected] > > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > > > > -- > Joseph Blomstedt <[email protected]> > Software Engineer > Basho Technologies, Inc. > http://www.basho.com/ > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
