hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinay (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 16:36:35 GMT

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

Vinay commented on HADOOP-10136:
--------------------------------

Thanks Steve for the input.
bq. Is the port the JMX server coming up on in use?
This is possible. But my concern was not this. Default JMX will use one more extra random
port along with the port configured via *-Dcom.sun.management.jmxremote.port*. 

I will try to implement suggestions you given.

bq. have a way to query the server for the port in use
Do you mean, querying this via RPC..?

> 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