1.4.2: 'riak-admin reip' no longer works?

Joe Caswell jcaswell at basho.com
Mon Oct 21 12:57:06 EDT 2013


Reip is the old, evil way to do it that is fraught with peril.  When it
works it works spectacularly, and when it doesn't, it fails spectacularly.
The only use case left for reip is when you have simultaneously changed the
node name for every node in the cluster, such as when loading an entire
cluster's worth of backups to new machines.  Since a node will not be able
to start unless it is a member of the ring it currently holds, and
`riak-admin cluster [force-]replace` requires there to be at least one node
in the cluster running,  reip is the only option to get the first node
started.  After the first node, all the rest can be handled with cluster
replace.

Joe Caswell

From:  Brady Wetherington <brady at bespincorp.com>
Date:  Monday, October 21, 2013 12:26 PM
To:  Dave Brady <dbrady at weborama.com>
Cc:  Riak Users Mailing List <riak-users at lists.basho.com>
Subject:  Re: 1.4.2: 'riak-admin reip' no longer works?

Huh. I thought we were supposed to use "force-replace" instead of "reip"?

I remember having a discussion a few months back about the documentation and
we cleared it up a little.

Is "reip" the same as "force-replace", or is it more..."quick-and-dirty?" Is
it deprecated?

-B.


On Mon, Oct 21, 2013 at 11:33 AM, Dave Brady <dbrady at weborama.com> wrote:
> Thanks for clarifying it!
> 
> This functionality has been *great* to create quick-and-dirty test rings.
> 
> --
> Dave Brady
> 
> 
> From: "Jared Morrow" <jared at basho.com>
> To: "Dave Brady" <dbrady at weborama.com>
> Cc: "Riak Users Mailing List" <riak-users at lists.basho.com>
> Sent: Lundi 21 Octobre 2013 16:42:22
> 
> Subject: Re: 1.4.2: 'riak-admin reip' no longer works?
> 
> We actually discussed this recently, my understanding of reip was clearly not
> complete, and Joe Caswell put me on the right track.  'reip' will continue to
> stick around.
> 
> -Jared
> 
> 
> On Mon, Oct 21, 2013 at 8:23 AM, Dave Brady <dbrady at weborama.com> wrote:
>> No problem, Jared!  I'm happy it was a very simple fix.
>> 
>> What concerns me is that the 'cluster' commands do not have an analogous
>> feature: 'replace' does not do the same thing as 'reip'.
>> 
>> Is it truly a foregone conclusion that 'reip' is going away?
>> 
>> --
>> Dave Brady
>> 
>> 
>> From: "Jared Morrow" <jared at basho.com>
>> To: "Dave Brady" <dbrady at weborama.com>
>> Cc: "Riak Users Mailing List" <riak-users at lists.basho.com>
>> Sent: Lundi 21 Octobre 2013 16:17:52
>> Subject: Re: 1.4.2: 'riak-admin reip' no longer works?
>> 
>> 
>> This was a mistake on my part, if you s/up/down/ (node_down_check) on that
>> line it will correctly ensure the node is down before running reip.  Sorry
>> about that, clearly 'reip' is not heavily used with the new cluster commands
>> and it slipped under the radar for all these months.
>> 
>> -Jared
>> 
>> 
>> On Mon, Oct 21, 2013 at 7:48 AM, Dave Brady <dbrady at weborama.com> wrote:
>>> Thanks to Joe Caswell at Basho: just have to comment out line 382
>>> (node_up_check) in the riak-admin script.
>>> 
>>> --
>>> Dave Brady
>>> 
>>> ----- Original Message -----
>>> From: "Dave Brady" <dbrady at weborama.com>
>>> To: riak-users at lists.basho.com
>>> Sent: Lundi 21 Octobre 2013 13:59:37
>>> Subject: 1.4.2: 'riak-admin reip' no longer works?
>>> 
>>> Hi everyone,
>>> 
>>> So, I went to copy /var/lib/riak/* from one five-node cluster to another, so
>>> that we could experiment on the data.
>>> 
>>> I did this fairly frequently in the past (< 1.4.0), and always used
>>> "riak-admin reip <old> <new>".
>>> 
>>> Now, when I try that command on our 1.4.2 ring, 'riak-admin' dies with "Node
>>> is not running!"
>>> 
>>> This confuses me, since "reip" requires the ring to be down, but the
>>> "riak-admin" script is indeed expecting the local node to be running when
>>> using this option.
>>> 
>>> I see on the wiki that it is mentioned that "cluster replace" will replace
>>> "reip" in the future.  I hope not, since "cluster replace" does not provide
>>> the same functionality.
>>> 
>>> Anyone run into this and find a fix?  (Or I am missing something obvious?)
>>> 
>>> Thanks!
>>> 
>>> --
>>> Dave Brady
>>> 
>>> 
>>> _______________________________________________
>>> riak-users mailing list
>>> riak-users at lists.basho.com
>>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>>> 
>>> _______________________________________________
>>> riak-users mailing list
>>> riak-users at lists.basho.com
>>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>> 
>> 
> 
> 
> 
> _______________________________________________
> riak-users mailing list
> riak-users at lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
> 

_______________________________________________ riak-users mailing list
riak-users at lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20131021/3126fa91/attachment.html>


More information about the riak-users mailing list