[
https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013968#comment-14013968
]
stack commented on HBASE-10289:
-------------------------------
[~tianq] Thank you for the nice patch and excellent doc! Should
bin/hbase-env.sh comments be amended around JMX? Does the old way of setting
up JMX will work? If so, should the doc mention it as alternative (though
refer back to why it is inferior) and should bin/hbase-env.sh comments point
into the hbase refguide for an alternative that allows setting explicit,
unchanging ports?
Nice work [~tianq]
> 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
> Assignee: Qiang Tian
> Priority: Minor
> Labels: stack
> Fix For: 0.99.0
>
> Attachments: HBASE-10289-v4.patch, HBASE-10289.patch,
> HBASE-10289_1.patch, HBASE-10289_2.patch, HBASE-10289_3.patch,
> HBase10289-master.patch, hbase10289-master-v1.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.2#6252)
