hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
Date Fri, 17 Jan 2014 15:53:19 GMT

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

stack commented on HBASE-10289:
-------------------------------

Tell me more [~nijel]  In hbase-env.sh in trunk you can specify ports for JMX (IIRC).  Or
are you talking about fixing the RMI madness where it picks a random port to respond?  With
this patch in place, can we remove the talk in hbase-env.sh of flags for starting JMX?  What
happens if someone passes the flags?  Will we have two JMX servers running?

Thanks for doing this.



> 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)

Mime
View raw message