[
https://issues.apache.org/jira/browse/FLINK-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273740#comment-15273740
]
ASF GitHub Bot commented on FLINK-1502:
---------------------------------------
Github user zentol commented on the pull request:
https://github.com/apache/flink/pull/1947#issuecomment-217368732
@rmetzger you are correct that you're job failed since the previous one
wasn't cleaned up yet. Should you try to run 2 identical jobs in parallel it
will fail, since 2 jobs would use the same metrics due to name clashes. Note
that in this version this also occurs when 2 operators have the same name. I
have some additional functionality coming up that would allow you to circumvent
this issue.
@ankitcha The problem with multiple reporters is our configuration, it only
supports single-line key-value pairs, and you need to know the exact key to
access it. In order to configure multiple reporters you would either need a
nested structure (which is not supportet), or index the configuration keys
(metrics.reporter.1.class) and add a new parameter containing the indices to
use (e.g. metrics.reporter: 0, 1), which isn't particularly user-friendly. The
metric system itself could deal with multiple reporters with minor
modifications; it's all about the configuration.
> Expose metrics to graphite, ganglia and JMX.
> --------------------------------------------
>
> Key: FLINK-1502
> URL: https://issues.apache.org/jira/browse/FLINK-1502
> Project: Flink
> Issue Type: Sub-task
> Components: JobManager, TaskManager
> Affects Versions: 0.9
> Reporter: Robert Metzger
> Assignee: Chesnay Schepler
> Priority: Minor
> Fix For: pre-apache
>
>
> The metrics library allows to expose collected metrics easily to other
> systems such as graphite, ganglia or Java's JVM (VisualVM).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
