[
https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875024#comment-13875024
]
nijel commented on HBASE-10289:
-------------------------------
pls ignore previous comment..
bq. Tell me more nijel In hbase-env.sh in trunk you can specify ports for JMX
(IIRC).
- Even if we specify the port one of the port will be random.
bq. can we remove the talk in hbase-env.sh of flags for starting JMX?
- Yes. After this patch we need not specify the flags in hbase-env.sh
bq. What happens if someone passes the flags? Will we have two JMX servers
running?
- Yes, 2 JMX servers will be running. In both the servers beans will be
registered.
The idea behind this patch is to give a option to user to control the ports
used by JMX server.
> Avoid random port usage by default JMX Server. Create Custome JMX server
> ------------------------------------------------------------------------
>
> Key: HBASE-10289
> URL: https://issues.apache.org/jira/browse/HBASE-10289
> Project: HBase
> Issue Type: Improvement
> Reporter: nijel
> Priority: Minor
> Attachments: HBASE-10289.patch
>
>
> If we enable JMX MBean server for HMaster or Region server through VM
> arguments, the process will use one random which we cannot configure.
> This can be a problem if that random port is configured for some other
> service.
> This issue can be avoided by supporting a custom JMX Server.
> The ports can be configured. If there is no ports configured, it will
> continue the same way as now.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
