Re: logging 'failed' tuples in mastercoord-bg0

2014-05-28 Thread P. Taylor Goetz
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,

Re: logging 'failed' tuples in mastercoord-bg0

2014-05-28 Thread Raphael Hsieh
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 ptgo...@gmail.com wrote: Silent replays are usually a

Re: $mastercoord-bg0

2014-05-22 Thread Raphael Hsieh
Also is there any way to look at logs for this master coordinator spout ? I'd like to be able to see what exactly is failing. Currently my mastercoord-bg0 spout says that there are 20 things failing, but there are no error messages displayed. and I don't see anything when I ssh into the box

$mastercoord-bg0

2014-05-21 Thread Raphael Hsieh
what does the $mastercoord-bg0 represent ? It seems to have much less work that my bolt spout. Also how can I set the parallelism of this master spout ? when my other bolts are emitting and acking millions of tuples, this master spout only emits/acks a couple dozen. Also currently something