Hello everybody!
Maybe some of you has faced my problem before. I would be glad to
receive any ideas.
I'm trying to perform a rolling upgrade of nodes one by one.
I'm stopping one node and update configuration file to meet
compatibility with riak 0.14. Namely I set
the following options in riak_kv section:
{legacy_keylisting, true},
{mapred_system, legacy},
{vnode_vclocks, false},
Then I install riak 1.1 and start it. But with no success as I
understood the newly updated node can't bring up its vnodes...
The error log tells me the following:
11:20:36.096 [error] Supervisor riak_kv_sup had child
riak_kv_vnode_master started with
riak_core_vnode_master:start_link(riak_kv_vnode, riak_kv_legacy_vnode,
riak_kv) at <0.491.0> exit with reason bad argument in call to
ets:lookup(riak_core_node_watcher, {by_node,'[email protected]'}) in
riak_core_node_watcher:internal_get_services/1 in context child_terminated
11:20:36.104 [error] gen_server riak_kv_vnode_master terminated with
reason: bad argument in call to ets:lookup(riak_core_node_watcher,
{by_node,'[email protected]'}) in
riak_core_node_watcher:internal_get_services/1
11:20:36.132 [error] CRASH REPORT Process riak_kv_vnode_master with 0
neighbours crashed with reason: bad argument in call to
ets:lookup(riak_core_node_watcher, {by_node,'[email protected]'}) in
riak_core_node_watcher:internal_get_services/1
11:20:36.132 [error] Supervisor riak_kv_sup had child
riak_kv_vnode_master started with
riak_core_vnode_master:start_link(riak_kv_vnode, riak_kv_legacy_vnode,
riak_kv) at <0.1474.0> exit with reason bad argument in call to
ets:lookup(riak_core_node_watcher, {by_node,'[email protected]'}) in
riak_core_node_watcher:internal_get_services/1 in context child_terminated
11:20:36.133 [error] gen_server riak_kv_vnode_master terminated with
reason: bad argument in call to ets:lookup(riak_core_node_watcher,
{by_node,'[email protected]'}) in
riak_core_node_watcher:internal_get_services/1
11:20:36.134 [error] CRASH REPORT Process riak_kv_vnode_master with 0
neighbours crashed with reason: bad argument in call to
ets:lookup(riak_core_node_watcher, {by_node,'[email protected]'}) in
riak_core_node_watcher:internal_get_services/1
11:20:36.134 [error] Supervisor riak_kv_sup had child
riak_kv_vnode_master started with
riak_core_vnode_master:start_link(riak_kv_vnode, riak_kv_legacy_vnode,
riak_kv) at <0.1475.0> exit with reason bad argument in call to
ets:lookup(riak_core_node_watcher, {by_node,'[email protected]'}) in
riak_core_node_watcher:internal_get_services/1 in context child_terminated
11:20:36.136 [error] Supervisor riak_kv_sup had child
riak_kv_vnode_master started with
riak_core_vnode_master:start_link(riak_kv_vnode, riak_kv_legacy_vnode,
riak_kv) at <0.1475.0> exit with reason reached_max_restart_intensity in
context shutdown
PS. I tuned up all the limits and open ports values...
Waiting for you help and
thank you!
Denis
_______________________________________________
riak-users mailing list
[email protected]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
