Riak crashed with MANIFEST not found

Nam Nguyen nam at tinyco.com
Tue May 29 12:20:19 EDT 2012

Thank you very much Justin.

Here's another command to hopefully speed up the handoff process.

On any of the node, attach to Erland console, then:

rp([{N, rpc:call(N, application, get_env, [riak_core, handoff_concurrency])} || N <- [node() | nodes()]]).

This command will show the current handoff_concurrency number. The result could be:

[{'riak at',{ok,1}},                                                   
 {'riak at',{ok,1}},                                                   
 {'riak at',{ok,1}},                                                   
 {'riak at',{ok,1}}]

Then, to change handoff_concurrency to, say, 4, issue this command:

rp(rpc:multicall([node() | nodes()], application, set_env, [riak_core, handoff_concurrency, 4])).

Justin was very helpful to guide me along the process. He showed me those commands. Thanks again, Justin!


On May 25, 2012, at 8:51 PM, jshoffstall wrote:

> Nam,
> To recap the upshot of our offline chat tonight:
> Though the leave operations on your cluster progressed fine, in the future I
> would just take the damaged nodes down, do the repair like I mentioned in
> the earlier post in this thread, and bring the nodes back up. No membership
> changes should be required.
> Justin Shoffstall
> Developer Advocate | Basho Technologies, Inc.
> --
> View this message in context: http://riak-users.197444.n3.nabble.com/Riak-crashed-with-MANIFEST-not-found-tp4015987p4016240.html
> Sent from the Riak Users mailing list archive at Nabble.com.
> _______________________________________________
> riak-users mailing list
> riak-users at lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

More information about the riak-users mailing list