[
https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13960800#comment-13960800
]
Demai Ni commented on HBASE-10289:
----------------------------------
[~stack], thanks for reviewing the patch.
I am not familiar with JMX setting. from my cluster:
{code}
export HBASE_JMX_BASE="-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=true
-Dcom.sun.management.jmxremote.password.file=/opt/ibm/biginsights/conf/jmx/hbase/jmxremote.password
-Dcom.sun.management.jmxremote.access.file=/opt/ibm/biginsights/conf/jmx/hbase/jmxremote.access"
{code}
the value $HBASE_JMX_BASE is used to start others, like HMaster, TaskTracker.
Probably won't hurt to leave it there... Again, I am not familiar with
that(smile)
> 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
> 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
>
>
> 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)
