hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nijel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
Date Thu, 24 Apr 2014 05:25:16 GMT

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

nijel commented on HBASE-10289:
-------------------------------

Hi all,
Thanks for taking a look in to the patch
Sorry for late reply ..


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

this is not enabled by default. If we enable this 2 more ports needs to be configured. Will
this disturb the current users ?  If not i can do the changes..

bq.1)our QA has tested the patch cannot work. I'd think it is not a complete implementation,
other options(stuff in HBASE_JMX_BASE) including security are not considered. there is the
wheel already, I might not tend to recreate it..

This patch is pluggable JMX server. If we all agree can make changes to the scripts to make
it default and take care of removing the existing JMX parameters. 

bq.2)the real problem is the random ports that JMX opens could cause conflict. even if we
implement by ourselves, the random local attach port is still there – unless bug 8035404
is fixed.

The local ports are there for every service. Our RPC mechanism also associated with client
ports. But this can be configured to a range to avoid conflicts with the service ports (can
update this value /proc/sys/net/ipv4/ip_local_port_range).


bq.4)I tried google "hadoop port in use" and got quite a few hits..and the page ranking of
"default ports" is high might show user need a centralized management of ports from various
components.. anyway, just my thoughts..

i agree with this. Normally user will have a centralized client port management and specified
range of client ports.
But for RMI the port is taken as random and will not release it.
The issue we faced is say one port is configured for some service and that port is is acquired
by HBase process (JMX) which is not expected. This port is not falling in the ephemeral port
range configured.

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