[
https://issues.apache.org/jira/browse/FLINK-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15851611#comment-15851611
]
Chesnay Schepler commented on FLINK-5552:
-----------------------------------------
[~rmetzger] I couldn't think of a good way to implement this so far.
The easiest way to get the port to the TM/Frontend would be to just add a
metric for it. However, this would require a new/modified method in the
Reporter interface which would be a breaking change.
> Make the JMX port available through RESTful API
> -----------------------------------------------
>
> Key: FLINK-5552
> URL: https://issues.apache.org/jira/browse/FLINK-5552
> Project: Flink
> Issue Type: Improvement
> Components: Metrics, Webfrontend
> Reporter: david.wang
>
> Currently, JMXReporter will create a server for JMX viewer retrieving JMX
> stat. The port can be configured through configuration options, but for large
> cluster with many machines running many Flink instances and other processes,
> we can set a fixed port to JMX server, making it difficult to get the JMX
> port.
> This JIRA is to suggest adding an api at web frontend so that it is very easy
> to get the JMX port for JM and TM.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
