storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Phil Burress <philburress...@gmail.com>
Subject Re: Trouble with Acking After a Worker Fails
Date Fri, 04 Apr 2014 19:15:14 GMT
I have also observed this same behavior. Also looking for a solution to
this.
On Apr 4, 2014 6:58 AM, "Poling, Raymond" <raymond.poling@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.
>
>
>

Mime
View raw message