When you send a tuple from the spout, it sets the message id in the acker. When a message fans out, it did logical xor of new tuple ids with the existing message id, and when tuples get acked their message id id xor'd into the same value again. This fanning out tuples should be quite light weight.
I've worked with a topology that had very very night fan outs but we did not use reliable messaging for this topology because of the time scale so it's not directly comparable. Maybe others who have experience with this setup can chime in. On May 14, 2015 1:45 AM, "Eran Chinthaka Withana" <eran.chinth...@gmail.com> wrote: > Hi Nathan > > No I still didn't try jstack > > But I'm just wondering whether this is something that could within storm > itself due to the amount of messages being emitted for one spout message. > Wondering whether the internal executor buffers or ackers are having > issues. Have you seen this before? Also, is this something storm could > handle you think? > > Thanks, > Eran Chinthaka Withana > > On Wed, May 13, 2015 at 6:34 PM, Nathan Leung <ncle...@gmail.com> wrote: > >> Did you try running jstack to see what your threads are doing? >> >> On Wed, May 13, 2015 at 9:13 PM, Eran Chinthaka Withana < >> eran.chinth...@gmail.com> wrote: >> >>> Here is the complete config and topology builder code (written in >>> scala): http://pastebin.com/xhJGDsXn >>> >> >> >
