Hi Jorge, I suspect you’re seeing a harmless message resulting from a race condition in pipe worker supervision, but to confirm that — can you paste a snippet from your console.log showing this crash? It may appear something like the following:
20:35:33.789 [error] Supervisor riak_pipe_fitting_sup had child undefined started with riak_pipe_fitting:start_link() at <0.23055.9> exit with reason noproc in context shutdown_error If that turns out to be the case I suspect your protobuf connection timeouts are a something mitigable with a bit more system tuning. I’d suggest quickly reviewing the tuning guidelines in the `operations’ section of docs.basho.com ( link: http://docs.basho.com/riak/latest/ops/tuning/linux/ ). -- Alex Berghage On September 15, 2014 at 11:52:15 AM, Jorge Garrido gomez ([email protected]) wrote: Hello My team detected the next error on our riak cluster: 2014-09-15 11:09:14 =SUPERVISOR REPORT==== Supervisor: {local,riak_pipe_fitting_sup} Context: shutdown_error Reason: noproc Offender: [{pid,<0.12743.378>},{name,undefined},{mfargs,{riak_pipe_fitting,start_link,[]}},{restart_type,temporary},{shutdown,2000},{child_type,worker}] We don’t know what is it, but sometimes our local application is disconnected from riak protobuffers client with a reqpb_timeout, we use erlang client, the next are the configuration for our cluster: Riak version 1.4.2. Cluster with 4 nodes. Enable search on all nodes. All default settings on vm.args and app.config I hope you can help us, _______________________________________________ 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
