The UI reports values in multiples of 20. The counts are not exactly raw counts but samples. (I think it is possible configure storm to sample every tuple to get a more accurate count, but with a huge hit to performance).
So yes, this is expected behaviour. On Fri, Feb 13, 2015 at 5:02 AM, Michael Writescode < [email protected]> wrote: > I have a few very simple bolts in my topology that perform a filtering > function. I would exect the tuples emitted field reported in the Storm UI > to always be less than the tuples executed field because of this logic. > > However I often observe the Emitted column reporting numbers slightly > higher than the Executed column when the filter is letting most data > through. Typically the difference is only about 20-60 tuples (always a > multiple of 20). > > Example: one filter is currently reporting 219700 tuples executed in the > last 10 minutes and 219720 emitted in the same time frame. No tuples failed > anywhere in my topology. > > Is this expected behavior? >
