You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2017/02/02 16:18:51 UTC

[jira] [Commented] (FLINK-5552) Make the JMX port available through RESTful API

    [ https://issues.apache.org/jira/browse/FLINK-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850107#comment-15850107 ] 

Robert Metzger commented on FLINK-5552:
---------------------------------------

[~Zentol] any thoughts on this issue?
I wonder if we can create some infrastructure for a metric reporter to advertise its ports / hostnames etc?

Getting the JMX port for the TaskManagers is probably pretty hard because the reporter instances would need to report the port back to the TaskManager.

> 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)