On Wed, Aug 7, 2013 at 4:37 AM, Shane McEwan <sh...@mcewan.id.au> wrote: > It doesn't seem to be causing us any problems and @beerriot's comments on > #49 seem to indicate the messages are safe to ignore so that's what I'll do > until we're ready to upgrade.
Indeed, the problem is harmless, other than generating log spam. Unfortunately, while the patches that Jared mentioned address similar errors, the specific "exit with reason noproc in context shutdown_error" might still happen on 1.3.2 and 1.4.x. It's a race in the shutdown monitoring logic of Erlang/OTP's 'supervisor' module (see my last comment on riak_pipe issue #49 [1]). The fix requires more restructuring than we had time to do for the 1.4 release. Despite the 'error' level of the log (which is set by code we don't control), the race is harmless, and the correct logical thing (making sure the process is dead) is happening. -Bryan [1] https://github.com/basho/riak_pipe/issues/49#issuecomment-17147806 _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
