I am running 1.0 release snapshot right now and for certain mapreduce
functions, I am getting many errors like that as well on some (but not
all) mapreduce queries.
any hints on where to start looking to trouble-shoot this issue?
Here's one of the queries that consistently generates series of
'fitting_died' log messages:
{
"inputs":{
"bucket":"test",
"index":"integer_int",
"start":20000000001,
"end":200000000200
},
"query":[
{"map":{"language":"javascript",
"source":"function(v) {
if (v.values){
data = Riak.mapValuesJson(v)[0];
return [data];
}else{
return[];
}
}",
"keep":true
}
},
{"reduce":{"language":"javascript",
"source": "function(v){ return v;}"}},
{"reduce":{"language":"javascript",
"source":"function(v) {
v.sort(function(a,b) {return
b.integer < a.integer});
return v;
}"
}
}
],"timeout": 9000
}
produces over hundred of " "Supervisor riak_pipe_vnode_worker_sup had
child at module undefined at <0.28835.0> exit with reason fitting_died
in context child_terminated" entries in log file and returns 'timeout'
On Sun, Sep 11, 2011 at 3:38 PM, Ryan Caught <[email protected]> wrote:
> Hi,
> I'm testing out a rolling upgrade with 1.0 pre2 and found that when I turn
> off legacy_keylisting Riak crashes on me. Things work fine when
> legacy_keylisting is turned on.
> Here is what I found in the crash log.
>>
>> 2011-09-11 07:15:44 =SUPERVISOR REPORT====
>> Supervisor: {local,riak_pipe_fitting_sup}
>> Context: child_terminated
>> Reason: killed
>> Offender:
>> [{pid,<0.2725.0>},{name,undefined},{mfargs,{riak_pipe_fitting,start_link,undefined}},{restart_type,temporary},{shutdown,2000},{child_type,worker}]
>
> I'm using Ubuntu with Ripple (0.9.5).
>
> Ryan
> _______________________________________________
> riak-users mailing list
> [email protected]
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
>
_______________________________________________
riak-users mailing list
[email protected]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
