Re: If tuples come in too fast for bolts to process, does Zookeeper keep it in a queue?

Hi! You welcome. nextTuple and the ack method are called in the same thread by the framework. So if you have heavy computation in the next tuple, your ack method will never be called and the buffers that are responsible for receiving the ack messages will not be emptied. The nextTuple acts as

Re: If tuples come in too fast for bolts to process, does Zookeeper keep it in a queue?

Thanks Florin. It does indeed seem to be a memory problem. Turns out that there were no ack's happening either because I was emitting from a while loop in nextTuple() and it never left the nextTuple() function. On Fri, May 6, 2016 at 11:59 AM, Spico Florin wrote: > Hello!

If tuples come in too fast for bolts to process, does Zookeeper keep it in a queue?

Hi, I have a topology where if a spout emits 1 tuple, a Bolt-A takes that tuple and emits 20 tuples. The next Bolt-B takes Bolt-A's tuples and emits 50 more tuples for each of Bolt-A's tuples. Tuples are always anchored. *Question:* When a light-weight spout emits a few tuples and Bolt-B has to