Glad to have been able to help. On Fri, Mar 22, 2013 at 12:11 PM, Godefroy de Compreignac <[email protected]> wrote: > Thank you a lot for your help! > > I guess I forgot to restart one node after the configuration of a new memory > backend. > Anyway, I upgraded all my nodes to Riak 1.3.1, and everything seems to be > working great! > > Godefroy > > > 2013/3/22 Evan Vigil-McClanahan <[email protected]> >> >> OK, so there's a lot going on there. >> >> > 2013-03-22 12:02:18.719 [error] <0.16959.2526> gen_server <0.16959.2526> >> > terminated with reason: no function clause matching >> > riak_core_pb:encode({ts,{1363,205559,674898}}, >> > >> > {{ts,{1363,205559,674898}},<<131,104,7,100,0,8,114,95,111,98,106,101,99,116,109,0,0,0,14,101,...>>}) >> > line 40 >> >> This one is usually because you have different settings on the memory >> backend on two nodes (one with a ttl, the other without). Typically >> the solution here is to make sure that the settings are the same >> across the cluster and then do a rolling restart of the cluster. >> >> >> > 2013-03-22 11:28:53.379 [error] <0.28559.1189> gen_fsm <0.28559.1189> in >> > state active terminated with reason: no case clause matching >> > >> > {error,bad_crc,{state,[{<<"cache">>,riak_kv_memory_backend,{state,57458783,57450590,57442397,10737418240,31415183,43200}},{<<"storage-kazeo">>,riak_kv_bitcask_backend,{state,#Ref<0.0.461.178788>,"79925870791533753339264014289171727637433810944",[{data_root,"/data/riak/bitcask/storage-kazeo"},{read_write,true}],79925870791533753339264014289171727637433810944,"/data/riak/bitcask/storage-kazeo"}},{<<"storage-laprovence">>,riak_kv_bitcask_backend,{state,#Ref<0.0.461.178779>,"79925870791533753339...",...}},...],...}} >> > in riak_kv_vnode:do_diffobj_put/3 line 1059 >> > 2013-03-22 11:28:53.379 [error] >> > <0.15853.1198>@riak_core_handoff_receiver:handle_info:80 Handoff >> > receiver >> > for partition 79925870791533753339264014289171727637433810944 exited >> > abnormally after processing 5337 objects: >> > >> > {{{case_clause,{error,bad_crc,{state,[{<<"cache">>,riak_kv_memory_backend,{ >> >> This one looks like it might be because of some bad data left over >> from your filling up of the disk. It's possible that upgrading to 1.3 >> will help here, it has better handling of corrupted data in bitcask. >> >> If that isn't an option right now, let me know, there may be some >> other ways to get the corrupted values out of the cluster. > >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
