G'day!

We're about to start upgrading our Riak clusters from 1.2.1 to 1.3.1 and I have a couple of questions about the upgrade process.

Firstly, the new "enable_health_checks" config option. It's not clear what impact this option will have on a busy cluster. The way I read it, if a riak_kv_vnode message queue goes over the "vnode_mailbox_limit" DisableThreshold then the riak_kv service is disabled. Doesn't this effectively take the node down? If you have a busy cluster isn't it possible that all nodes could hit this limit around the same time and bring the whole cluster down? Especially if you're running close to the limit and one node gets taken offline then the other nodes try to take up the slack which puts them over the threshold. Or am I misunderstanding this feature?

Is there any way to query the riak_kv_vnode message queue length to get an idea of how close we are to hitting the limit?

Secondly, reformatting the indexes to fix the 2i integer encoding problem. Do I need to run the "riak-admin reformat-indexes" on each node or just once for the whole cluster?

Thanks!

Shane.

_______________________________________________
riak-users mailing list
[email protected]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Reply via email to