[
https://issues.apache.org/jira/browse/FLINK-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rong Rong updated FLINK-5552:
-----------------------------
Comment: was deleted
(was: Yes. I think having it in the log is possible. however, based on my
experience. we need to configure extra logging options in order to make it work:
1. we use log4j / slf4j as our main logging mechanism (I think this is also one
of the 2 default supported logger (logback/log4j))
2. com.sun.management.jmxremote.* uses java util logging instead. so we have to
make extra effort: configuring a SLF4JBridgeHandler as part of the java util
logging properties.
This is a bit cumbersome.
Regardless. I think I figured out a way to start the JMX server - I push the
code snippet in
https://github.com/apache/flink/compare/master...acbb9b26b6745274dbb33209334e8bdf9e919fea
--> this is far from ready as there are many config / testing involve. but
gives the gist on what I think would work.
Please kindly take a look.)
> 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
> Assignee: Rong Rong
> 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)
