[jira] [Updated] (STORM-3684) receive-queue V2 metrics shouldn't have "_system" as componentId if it is from a system task

["Ethan Li (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/STORM-3684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ethan Li updated STORM-3684:
----------------------------
    Summary: receive-queue V2 metrics shouldn't have "_system" as componentId if it is from a system task  (was: receive-queue V2 metrics shouldn't have "_system" as componentId)

> receive-queue V2 metrics shouldn't have "_system" as componentId if it is from a system task
> --------------------------------------------------------------------------------------------
>
>                 Key: STORM-3684
>                 URL: https://issues.apache.org/jira/browse/STORM-3684
>             Project: Apache Storm
>          Issue Type: Bug
>            Reporter: Rui Li
>            Assignee: Rui Li
>            Priority: Minor
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> When storm registers receive-queue for executors,
> [https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apache/storm/daemon/worker/WorkerState.java#L722-L724]
> it set componentId as "__system" for any task. This is wrong for V2 metrics.
> V1 metrics are fine since the component Id used for V1 metric is not from the same place.
> [https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apache/storm/executor/Executor.java#L342-L343]
> It is from the member variable of the executor object.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)