[ https://issues.apache.org/jira/browse/FLINK-16789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067714#comment-17067714 ]
Rong Rong edited comment on FLINK-16789 at 3/26/20, 3:03 PM: ------------------------------------------------------------- Yes. I agree. in fact the {{JMXServer}} class in the reporter can be directly reused. I would create a PR for the refactoring against FLINK-5552 to split out the JMXServer and put it in the cluster level, and then for this ticket I would only need to add the JMXRMI related components. was (Author: rongr): Yes. I agree. in fact the {{JMXServer}} class in the reporter can be directly reused. I would create a PR for the refactoring against FLINK-5552 to split out the JMXServer and put it in the cluster level, and then I would only need to add the JMXRMI related components. > Support JMX RMI port retrieval via JMXConnectorServer > ----------------------------------------------------- > > Key: FLINK-16789 > URL: https://issues.apache.org/jira/browse/FLINK-16789 > Project: Flink > Issue Type: New Feature > Components: Runtime / Coordination, Runtime / Task > Affects Versions: 1.11.0 > Reporter: Rong Rong > Assignee: Rong Rong > Priority: Major > > Currently there are no easy way to assign jmxrmi port to a running Flink job. > The typical tutorial is to add the following to both TM and JM launch env: > {code:java} > -Dcom.sun.management.jmxremote > -Dcom.sun.management.jmxremote.port=9999 > -Dcom.sun.management.jmxremote.local.only=false > {code} > However, setting the jmxremote port to 9999 is not usually a viable solution > when Flink job is running on a shared environment (YARN / K8s / etc). > setting *{{-Dcom.sun.management.jmxremote.port=0}}* is the best option > however, there's no easy way to retrieve such port assignment. We proposed to > use JMXConnectorServerFactory to explicitly establish a JMXServer inside > *{{ClusterEntrypoint}}* & *{{TaskManagerRunner}}*. > With the JMXServer explicitly created, we can return the JMXRMI information > via either REST API or WebUI. -- This message was sent by Atlassian Jira (v8.3.4#803005)