I also discovered MR issues during a rolling upgrade to 1.1.0 last
night. We had so many MR errors that the 1.1 node crashed altogether,
and I had to roll it back to 1.0.3. Basho support is working on that
problem.
2012-02-22 00:56:16.429 [error] <0.1615.0> gen_server
riak_pipe_vnode_master terminated with reason: no function clause
matching
riak_core_vnode_master:handle_call({return_vnode,{riak_vnode_req_v1,479555224749202520035584085735030365824602865664,{raw,#Ref<6584.0.7263.108930>,...},...}},
{<6604.7292.421>,#Ref<6604.0.6697.250987>},
{state,undefined,undefined,riak_pipe_vnode,undefined})
2012-02-22 00:56:16.431 [error] <0.1615.0> CRASH REPORT Process
riak_pipe_vnode_master with 0 neighbours crashed with reason: no
function clause matching
riak_core_vnode_master:handle_call({return_vnode,{riak_vnode_req_v1,479555224749202520035584085735030365824602865664,{raw,#Ref<6584.0.7263.108930>,...},...}},
{<6604.7292.421>,#Ref<6604.0.6697.250987>},
{state,undefined,undefined,riak_pipe_vnode,undefined})
Anything like these messages in your logs?
--Kyle
On 02/22/2012 02:35 PM, heffergm wrote:
After upgrading to 1.1, we've had all kinds of MR issues (essentially all
failing). I'm seeing tons of these in the logs. Any ideas? We've rolled back
in the meantime:
2012-02-22 03:12:59.664 [error]<0.354.0>@riak_pipe_vnode:new_worker:763
Pipe worker startup failed:fitting was gone before startup
--
View this message in context:
http://riak-users.197444.n3.nabble.com/1-1-upgrade-woes-tp3768092p3768092.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
