Hi Daniil,
You should mark the claimant node as down.
Run the following command on another node:
riak-admin down riak@<ip-address>
Regards,
Ciprian
On Wed, Apr 23, 2014 at 12:13 PM, Daniil Churikov <ddo...@gmail.com> wrote:
> Hello riak users.
>
> We have a riak-1.3.2 cluster with 3 nodes. One of this node was physically
> shut down, and now any cluster operations fails with reason:
>
> # riak-admin cluster force-remove riak@10.3.12.80
> Attempting to restart script through sudo -H -u riak
> Remove failed, see log for details
>
> 2014-04-18 08:52:38.639 [error]
> <0.18341.8>@riak_core_console:stage_remove:234 Remove failed
> exit:{{nodedown,'riak@10.3.12.80'},{gen_server,call,[{riak_core_claimant,'
> riak@10.3.12.80'},{stage,'riak@10.3.12.80',remove},infinity]}}
>
> ==> error.log <==
> 2014-04-18 08:52:38.639 [error]
> <0.18341.8>@riak_core_console:stage_remove:234 Remove failed
> exit:{{nodedown,'riak@10.3.12.80'},{gen_server,call,[{riak_core_claimant,'
> riak@10.3.12.80'},{stage,'riak@10.3.12.80',remove},infinity]}}
>
> As I understood this node was a claimant node and all cluster operations
> must be done by this node. The question is, how should I change claimant in
> order to fix cluster operations?
>
>
>
> --
> View this message in context:
> http://riak-users.197444.n3.nabble.com/change-ring-claimant-tp4031018.html
> Sent from the Riak Users mailing list archive at Nabble.com.
>
> _______________________________________________
> 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
