Your image looks consistent with a very high value for max spout pending. Is there any chance that it is set manually on the spout when you are building your topology? On Jan 21, 2015 8:07 AM, "Margus Roo" <[email protected]> wrote:
> I made some pictures to describe the situation > > upload topology to storm server > > http://margus.roo.ee/wp-content/uploads/2015/01/Screenshot-2015-01-21-15.02.39.png > > storm UI > > http://margus.roo.ee/wp-content/uploads/2015/01/Screenshot-2015-01-21-15.03.13.png > > pending = 1 > > http://margus.roo.ee/wp-content/uploads/2015/01/Screenshot-2015-01-21-15.03.36.png > > any comments. I hoped to see same number behind spout emitted and ack > > Margus (margusja) Roohttp://margus.roo.ee > skype: margusja > +372 51 480 > > On 21/01/15 14:57, Nathan Leung wrote: > > Your understanding is correct. Note that it is per spout task, so if you > have 10 tasks then you could have 10 tuples in queue simultaneously. Are > your emits and acks for topology or spout only? Also note that if your bolt > does not emit using the incoming tuple as an anchor then storm will mark > the tuple tree as finished and your spout will be able to emit another > tuple. > On Jan 21, 2015 7:50 AM, "Margus Roo" <[email protected]> wrote: > >> Hi >> >> I have topology.max.spout.pending = 1. >> but i think my spout emits much more than I want. In example there are >> 762400 emitted and >> 381200 ack. >> As I understand topology.max.spout.pending it allows configured numbers >> of pending messages in spouts output queue in the time. So if >> topology.max.spout.pending = 1 then there can be only one message in the >> queue? >> >> -- >> Margus (margusja) Roohttp://margus.roo.ee >> skype: margusja >> +372 51 480 >> >> >
