hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10136) Custom JMX server to avoid random port usage by default JMX Server
Date Fri, 29 Nov 2013 10:19:40 GMT

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

Steve Loughran commented on HADOOP-10136:
-----------------------------------------

Is the port the JMX server coming up on in use? Surely it should be asking to listen on port
0 and let the OS find a port > 1024 where there is space.

If you are going to do a custom JMX server, I would like the option of letting it take a port
0 for an automatic port selection -but have a way to query the server for the port in use
-which is something the standard one doesn't let you do. Maybe also take a range of allowed
ports and scan through them until a free port can be used -which will allow ops teams to restrict
the open ports on a firewall to the same range

This is important for starting JMX in YARN containers, as you can't hard code any port bindings
without risking port collision.

> Custom JMX server to avoid random port usage by default JMX Server
> ------------------------------------------------------------------
>
>                 Key: HADOOP-10136
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10136
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Vinay
>            Assignee: Vinay
>
> If any of the java process want to enable the JMX MBean server  then following VM arguments
needs to be passed.
> {code}
> -Dcom.sun.management.jmxremote
> -Dcom.sun.management.jmxremote.port=14005
> -Dcom.sun.management.jmxremote.local.only=false
> -Dcom.sun.management.jmxremote.authenticate=false
> -Dcom.sun.management.jmxremote.ssl=false{code}
> But the issue here is this will use one more random port other than 14005 while starting
JMX. 
> This can be a problem if that random port is used for some other service.
> So support a custom JMX Server through which random port can be avoided.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message