You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2020/08/03 20:30:00 UTC

[jira] [Closed] (FLINK-5552) Introduce JVM-wide JMX server

     [ https://issues.apache.org/jira/browse/FLINK-5552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chesnay Schepler closed FLINK-5552.
-----------------------------------
    Fix Version/s: 1.12.0
       Resolution: Fixed

master: 2b699d6cb20823cd3a437b49bc96f015f4c1b72e

> Introduce JVM-wide JMX server
> -----------------------------
>
>                 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
>              Labels: pull-request-available
>             Fix For: 1.12.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)