Error on crash.log
aberghage at gmail.com
Mon Sep 15 15:12:34 EDT 2014
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/ ).
On September 15, 2014 at 11:52:15 AM, Jorge Garrido gomez (zgbjgg at gmail.com) wrote:
My team detected the next error on our riak cluster:
2014-09-15 11:09:14 =SUPERVISOR REPORT====
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
riak-users at lists.basho.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the riak-users