sink_died error!

Sean Cribbs sean at basho.com
Fri Apr 6 10:04:01 EDT 2012


Zabrane,

That error will occur when a client that issued a MapReduce request
disconnected before the request completed ("sink_died" -- the sink is where
results are sent, namely the client). It is entirely normal to see that
error.

On Fri, Apr 6, 2012 at 9:37 AM, Zabrane Mickael <zabrane3 at gmail.com> wrote:

> Hi guys,
>
> Anybody saw this error before?
>
> [...]
> 11:52:44.380 [info] alarm_handler: {set,{system_memory_high_watermark,[]}}
> 12:29:43.639 [error] gen_fsm <0.17794.0> in state wait_pipeline_shutdown
> terminated with reason: {sink_died,normal}
> 12:29:43.709 [error] CRASH REPORT Process <0.17794.0> with 0 neighbours
> crashed with reason: {sink_died,normal}
> 12:29:43.761 [error] Supervisor riak_pipe_builder_sup had child undefined
> started with {riak_pipe_builder,start_link,undefined} at <0.17794.0> exit
> with reason {sink_died,normal} in context child_terminated
>
> Regards,
> Zabrane
>
>
> _______________________________________________
> riak-users mailing list
> riak-users at lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>



-- 
Sean Cribbs <sean at basho.com>
Software Engineer
Basho Technologies, Inc.
http://basho.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.basho.com/pipermail/riak-users_lists.basho.com/attachments/20120406/df21e5a0/attachment.html>


More information about the riak-users mailing list