Fewer tuples Acked than Emitted
462 views
Skip to first unread message
James Kinley
Dec 30, 2011, 6:30:33 AM12/30/11
to storm-user
Hi,
I have a topology running with multiple bolts. The spout and first
bolt anchor their tuples. The second bolt ack's the processed tuples
but emits un-anchored tuples as I'm not concerned with guaranteeing
the tuples through the remaining bolts.
Why is it that the spout and the first and second bolts have different
values for Acked than they do for Emitted? I'd expected these values
to be the same considering I have no failed tuples.
E.g...
Spout: Emitted 2,940, Acked 1,460, Failed 0 (anchored)
Bolt 1: Emitted 2,940, Acked 1,480, Failed 0 (anchored)
Bolt 2: Emitted 2,920, Acked 1,480, Failed 0 (un-anchored)
Bolt 3: Emitted 180, Acked 1,460, Failed 0 (anchored)
Bolt 4: Emitted 80, Acked 180, Failed 0 (anchored)
...
__acker: Emitted 1,480, Acked 4,420, Failed 0
Thanks,
James.
I have a topology running with multiple bolts. The spout and first
bolt anchor their tuples. The second bolt ack's the processed tuples
but emits un-anchored tuples as I'm not concerned with guaranteeing
the tuples through the remaining bolts.
Why is it that the spout and the first and second bolts have different
values for Acked than they do for Emitted? I'd expected these values
to be the same considering I have no failed tuples.
E.g...
Spout: Emitted 2,940, Acked 1,460, Failed 0 (anchored)
Bolt 1: Emitted 2,940, Acked 1,480, Failed 0 (anchored)
Bolt 2: Emitted 2,920, Acked 1,480, Failed 0 (un-anchored)
Bolt 3: Emitted 180, Acked 1,460, Failed 0 (anchored)
Bolt 4: Emitted 80, Acked 180, Failed 0 (anchored)
...
__acker: Emitted 1,480, Acked 4,420, Failed 0
Thanks,
James.
Nathan Marz
Dec 30, 2011, 6:41:02 AM12/30/11
to storm...@googlegroups.com
There are implicit streams/bolts added to the topology for tracking tuples to guarantee message processing. The stats in the UI track all tuple emitted, including implicit streams and topologies. I go into more detail on this thread: http://groups.google.com/group/storm-user/browse_thread/thread/822be41e58fed298
dennis
Dec 31, 2011, 12:10:03 AM12/31/11
to storm-user
I think it is not nessary to display the stats of ackers on storm ui,
it is confused and you have to explain it again and again.
On Dec 30, 7:41 pm, Nathan Marz <nathan.m...@gmail.com> wrote:
> There are implicit streams/bolts added to the topology for tracking tuples
> to guarantee message processing. The stats in the UI track all tuple
> emitted, including implicit streams and topologies. I go into more detail
> on this thread:http://groups.google.com/group/storm-user/browse_thread/thread/822be4...
it is confused and you have to explain it again and again.
On Dec 30, 7:41 pm, Nathan Marz <nathan.m...@gmail.com> wrote:
> There are implicit streams/bolts added to the topology for tracking tuples
> to guarantee message processing. The stats in the UI track all tuple
> emitted, including implicit streams and topologies. I go into more detail
>
> On Fri, Dec 30, 2011 at 3:30 AM, James Kinley
> <jamesrobertkin...@gmail.com>wrote:
> On Fri, Dec 30, 2011 at 3:30 AM, James Kinley
songhe yang
Dec 31, 2011, 12:28:56 AM12/31/11
to storm-user
If the users can search the question in google/ google group first, it
would be much better.
would be much better.
Nathan Marz
Dec 31, 2011, 6:16:33 AM12/31/11
to storm...@googlegroups.com
It's important to be able to see everything that's happening in the topology. But I agree that it's confusing at first, and it would be useful to be able to just look at what the user code is doing, so I opened up this issue: https://github.com/nathanmarz/storm/issues/89
Reply all
Reply to author
Forward
0 new messages