The two bolts which emit/transfer 0 are likely your persistentAggregate
bolts. These are *sinks* so they don't logically emit/transfer tuples any
farther.
You can add add a name which will show up in the UI to help you see how
Trident compiles into your Storm topology.
.name("Aggregator 1")
.persistentAggregate(...)
.name("Aggregator 2")
.persistentAggregate(...)
-Cody
On Tue, May 20, 2014 at 7:38 PM, Harsha <[email protected]> wrote:
> Executed refers to number of incoming tuples processed.
>
> capacity is determined by (executed * latency) / window (time duration).
>
> UI should give you description of those stats if you hover over table
> headers.
>
>
>
>
> On Tue, May 20, 2014, at 03:36 PM, Raphael Hsieh wrote:
>
> I reattached the previous image in case it was too difficult to read before
>
>
> On Tue, May 20, 2014 at 3:31 PM, Raphael Hsieh <[email protected]>wrote:
>
> Hi I'm confused as to what each field in the StormUI represents and how to
> use the information.
> [image: Inline image 1]
>
> The bolts I have above are formed from trident. This is what operations I
> believe each bolt represents
> b-0 : .each(function) -> .each(filter)
> b-1 : .aggregate
> --split--
> b-2 : .persistentAggregate
> b-3 : .persistentAggregate
>
> What does it mean for the first two bolts to emit and transfer 0 ?
> What is the Capacity field ? What does that represent ?
> Does Execute refer to the tuples acked and successfully processed?
>
> Thanks
> --
> Raphael Hsieh
>
>
>
>
>
>
>
> --
> Raphael Hsieh
>
>
>
>
> Email had 2 attachments:
>
> - image.png
> - 41k (image/png)
> - NimbusUI.PNG
> - 22k (image/png)
>
>
--
Cody A. Ray, LEED AP
[email protected]
215.501.7891
