No. You need to consider your system more carefully. As a trivial example, imagine you have spout a -> bolt b -> bolt c, with bolt b splitting tuple into 10 tuples. Each component has 1 task. If each component takes 1ms, your latency will not be the sum of the per bolt latency because of your fan out. On Jul 29, 2015 11:25 AM, "Kashyap Mhaisekar" <[email protected]> wrote:
> Thanks Nathan. > > If I see the complete latency at spout is greater than the process > latencies of all bolts put together, does it mean that the ACKERS are a > problem and need to be increased? > > thanks > kashyap > > On Tue, Jul 28, 2015 at 7:30 PM, Nathan Leung <[email protected]> wrote: > >> The count is tracked from each spout task and does not include bolt fan >> out. If the setting is 100 and you have 8 spout tasks you can have 800 >> tuples from the spout in your system. >> On Jul 28, 2015 6:25 PM, "Kashyap Mhaisekar" <[email protected]> wrote: >> >>> Hi, >>> Does Max Spout Topology limitation apply to tuples emitted out of bolts >>> too? >>> For E.g.,. >>> 1. MAX_SPOUT_PENDING value is 1000 >>> 2. My Spout calls a bolt which emits 1000 tuples >>> >>> Does this mean there can be 1000X1000 tuples in the topology? Or does it >>> mean that only one tuple is emitted from Spout because each bolt emits 1000 >>> tuples? >>> >>> Thanks >>> kashyap >>> >> >
