Thanks Evan!
Is it really imperative that the name should be != than the old one?
Best regards
—
Sent from my iPhone
On Tue, Mar 18, 2014 at 8:47 PM, Evan Vigil-McClanahan
<emcclana...@basho.com> wrote:
> Probably the easiest thing would be to wait until the new machine is
> ready to join, add it with a nodename distinct from that of the last
> one, and force-replace the new node for the old, dead one.
> On Tue, Mar 18, 2014 at 1:03 PM, Edgar Veiga <edgarmve...@gmail.com> wrote:
>> Hello all!
>>
>> I have a 6 machine cluster with leveldb as backend, using riak 1.4.8
>> version.
>>
>> Today, the ssd of one of the machine's has failed and is not recoverable, so
>> I have already ordered a new one that should arrive by thursday!
>>
>> In the meanwhile what should I do? I have no backup of the old ssd data...
>> Should I remove the machine of the cluster and when the new ssd arrives join
>> the machine again?
>>
>> Best regards!
>>
>> _______________________________________________
>> riak-users mailing list
>> 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
