You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CRASH REPORT Process <0.15403.0> with 0 neighbours exited with reason: no function clause matching riak_kv_vnode:terminate({{{case_clause,{1,10000,<<"Lý<äUxªÏ">>}},[{riak_kv_vnode_status_mgr,get_counter_lease,3,[{file,...},...]},...]},...}, undefined) line 1155 in gen_fsm:terminate/7 line 600
Looks like it is possible for the vnode status file to be written as v1, and have a counter. Have asked for more information in IRC.
Basho-JIRA
changed the title
Vnode won't start with crash error for mixed vnode_status file
Vnode won't start with crash error for mixed vnode_status file [JIRA: RIAK-1857]
Jun 11, 2015
[~russelldb] Is this the same as PR1144 mentioned above (JIRA Riak-1857)? Should this be closed and done? I can see that PR1144 was merged but don't see PR1142 as merged in the comparison list I have from Jon M.
From Dams in #riak on IRC
Looks like it is possible for the vnode status file to be written as v1, and have a counter. Have asked for more information in IRC.
https://github.com/basho/riak_kv/blob/2.1/src/riak_kv_vnode_status_mgr.erl#L259
Maybe the scenario was run with vnode_counters, then turn off vnode_counters, then turn them on.
The text was updated successfully, but these errors were encountered: