You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@storm.apache.org by "Poling, Raymond " <ra...@citi.com> on 2014/04/04 12:57:07 UTC

Trouble with Acking After a Worker Fails

Sometimes when we run a three node topology, if a worker fails and comes back up, the entire topology will become sluggish, and messages will constantly be marked as failed. After changing the logging, we can determine that the topology is actually fully processing messages, however they are never being passed back to the acker to be acked. I've done searches to try and find solutions (other than don't let the worker fail) to fix the issue, but haven't found anything yet.

Re: Trouble with Acking After a Worker Fails

Posted by Phil Burress <ph...@gmail.com>.

I have also observed this same behavior. Also looking for a solution to
this.
On Apr 4, 2014 6:58 AM, "Poling, Raymond" <ra...@citi.com> wrote:

>  Sometimes when we run a three node topology, if a worker fails and comes
> back up, the entire topology will become sluggish, and messages will
> constantly be marked as failed. After changing the logging, we can
> determine that the topology is actually fully processing messages, however
> they are never being passed back to the acker to be acked. I've done
> searches to try and find solutions (other than don't let the worker fail)
> to fix the issue, but haven't found anything yet.
>
>
>