[
https://issues.apache.org/jira/browse/FLINK-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rong Rong updated FLINK-5552:
-----------------------------
Description:
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 cant
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.
was:
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.
> 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: Runtime / Metrics, Runtime / Web Frontend
> Reporter: david.wang
> Priority: Major
>
> 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 cant 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
(v8.3.4#803005)
