[
https://issues.apache.org/jira/browse/FLINK-7502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218989#comment-16218989
]
ASF GitHub Bot commented on FLINK-7502:
---------------------------------------
Github user mbode commented on the issue:
https://github.com/apache/flink/pull/4586
I mean in general it is probably not the best thing to just rely on the
port not being available as a consensus algorithm of who should claim which
port. Then again, I could not think of a straightforward way to coordinate
across Job/TaskManagers without using something external, which would probably
get too involved for a metrics-related component – maybe there is something I
am missing?
> PrometheusReporter improvements
> -------------------------------
>
> Key: FLINK-7502
> URL: https://issues.apache.org/jira/browse/FLINK-7502
> Project: Flink
> Issue Type: Improvement
> Components: Metrics
> Affects Versions: 1.4.0
> Reporter: Maximilian Bode
> Assignee: Maximilian Bode
> Priority: Minor
> Fix For: 1.4.0
>
>
> * do not throw exceptions on metrics being registered for second time
> * allow port ranges for setups where multiple reporters are on same host
> (e.g. one TaskManager and one JobManager)
> * do not use nanohttpd anymore, there is now a minimal http server included
> in [Prometheus JVM client|https://github.com/prometheus/client_java]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
