[
https://issues.apache.org/jira/browse/STORM-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002756#comment-14002756
]
ASF GitHub Bot commented on STORM-326:
--------------------------------------
Github user troyding commented on the pull request:
https://github.com/apache/incubator-storm/pull/118#issuecomment-43584255
Thank you for your advice @revans2 . I have added a new class named
ExclamationTopologyWithMetrics to reproduce the error. The newly added class is
based on the existed ExclamationTopology class. For testing, I set the
parallelism of the bolt named "exclaim1" to 3, and its task number to 6, and
the parallelism and task number of the second bolt named "exclaim2" to 2 and 6,
respectively. After running the topology, I got the following results:
As shown in the Figure, the task "4:exclaim1" has repeated twice of the
metric reporting, and the task "11:exclaim2" has repeated three times, as we
expected.
> task metric send repeatedly
> ---------------------------
>
> Key: STORM-326
> URL: https://issues.apache.org/jira/browse/STORM-326
> Project: Apache Storm (Incubating)
> Issue Type: Bug
> Affects Versions: 0.9.2-incubating, 0.9.1-incubating, 0.9.0.1
> Environment: CentOS 6.4 x64
> Reporter: troy ding
> Labels: metrics
> Attachments: executor-metrics.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Tasks send unnecessary Metrics and the repeated time is equal to the number
> of tasks in the executor, which runs them.
> Scenario: each time, a task will send repeated metric-tuples to the
> metricConsumer bolt (the 1st metric-tuple is normal, but the rest contain
> mostly zero-valued results).
> Causality: when a task receives a metric-tick-tuple, it "mistakenly" triggers
> all the tasks (belonging to the same executor) sending out metrics.
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
