[jira] [Commented] (HADOOP-10136) Custom JMX server to avoid random port usage by default JMX Server

["Colin Patrick McCabe (JIRA)" <ji...@apache.org>]

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

Colin Patrick McCabe commented on HADOOP-10136:
-----------------------------------------------

bq. [~steve_l@iseran.com]] Is the port the JMX server coming up on in use?

Unfortunately, some Hadoop daemons are using ports in the ephemeral range as if they were fixed ports.  For example, the DataNode uses port 50070 by default, which is in the Linux ephemeral range of 32768 to 61000.  In the long run, we'd like to migrate people away from using those ports.  But in the short run, reducing the ephemeral port usage would be a good thing.

> 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
>         Attachments: HADOOP-10136.patch
>
>
> 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)