It’s kind of implied from prior responses but just wanted to emphasize .. it
is not used if ACKing is disabled (I.e acker count = 0)
Sent from Yahoo Mail for iPhone
On Wednesday, April 3, 2019, 11:50 AM, Stig Rohde Døssing
wrote:
Supplementing the other great answers here, Storm checks
Supplementing the other great answers here, Storm checks max spout pending
before it invokes nextTuple on the spout. The spout executor calls
nextTuple in a loop. If the spout task has more pending tuples (i.e.
emitted but not acked or failed or timed out) than max spout pending, the
executor
Hi Jayant,
The MAX_SPOUT_PENDING is applied in each of the spouts.
Each spout take count of all the tuples it sends, increasing it for each emit
and decreasing it when it receive the final ack message for a “pending tuple”
(= a tuple that is sent but it’s still waiting an ack).
If the number
I’m pretty sure it’s per spout task. And they’re not coordinated. Each task
gets its own count.
Joshua
On Wed, Apr 3, 2019 at 4:50 AM Jayant Sharma
wrote:
> Hi,
>
> Can someone please explain at what point storm checks and applies
> MAX_SPOUT_PENDING limit. Also, is this limit applied per
