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 Thu, 03 Apr 2014 21:17:20 GMT

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

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

patch looks great to me.  Does it work for you [~nidmhbase]?

[~nijel] We turn JMX on by default but if I read your patch correctly, we will not be using
your fancy new JMX server by default.  Is that so?  Do we need to clean up what is in the
shell start scripts around JMX since now it an hbase-*.xml/HBaseConfiguration parameter rather
than an argument we pass the JVM.  What about security on the this new JMX Server?  Can we
specify a login for jmx on your server?  Thanks.

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

Mime
View raw message