RE: logging 'failed' tuples in mastercoord-bg0

[Simon Cooper <si...@featurespace.co.uk>]

Is there any other cause of silent replays? We’re seeing batch replays even though tuple timeouts are turned off completely, and max_spout_pending is 1...

From: Raphael Hsieh [mailto:raffihsieh@gmail.com]
Sent: 28 May 2014 23:08
To: user@storm.incubator.apache.org
Subject: Re: logging 'failed' tuples in mastercoord-bg0

thanks for your help Taylor,
Do you think you could point me to some documentation on where I can set those values in Storm Trident? I can't seem to find anything or figure that out.
Thanks

On Wed, May 28, 2014 at 2:58 PM, P. Taylor Goetz <pt...@gmail.com>> wrote:
"Silent replays" are usually a sign of batches timing out.

By default storm uses a timeout value of thirty seconds.

Try upping that value and setting TOPOLOGY_SPOUT_MAX_PENDING to a very low value like 1. In trident that controls how many batches can be in-flight at a time.

-Taylor

> On May 28, 2014, at 5:24 PM, Raphael Hsieh <ra...@gmail.com>> wrote:
>
> Is there a way to add logging to the master coordinator?
> For some reason my spout is failing batches and not giving me any error messages.
> The log files on the host don't provide any error messages and I'm not sure where the logic for this resides in Storm-Trident.
>
> Is there a particular string other than 'failed' that I can grep for?
>
> Thanks
> --
> Raphael Hsieh
>
>



--
Raphael Hsieh