[
https://issues.apache.org/jira/browse/FLINK-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355493#comment-15355493
]
ASF GitHub Bot commented on FLINK-1550:
---------------------------------------
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/2146
That is a known and intended behavior. It is the users responsibility to
make sure that no naming conflicts arise, either by providing unique
job/task/operator names or modifying the scope formats.
Regarding your suggestion, even if we exclude the disparity between the
name a user expects and the name we might provide, there is still the issue
that it (sadly) doesn't actually solve anything.
Assume 2 TaskManagers, both exporting a metric `MyJob.metric` and
`MyJob1.metric`.
You cannot guarantee that both versions of `MyJob.metric` actually belong
to the same job.
You can't even make the guarantee that all values a TM exposes as
`MyJob.metric` belong to a single job.
This problem also exists right; the only difference is that you only have 1
set of inconsistent data, and not 2.
> Show JVM Metrics for JobManager
> -------------------------------
>
> Key: FLINK-1550
> URL: https://issues.apache.org/jira/browse/FLINK-1550
> Project: Flink
> Issue Type: Sub-task
> Components: JobManager, Metrics
> Reporter: Robert Metzger
> Assignee: Chesnay Schepler
> Fix For: pre-apache
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
