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

Qiang Tian commented on HBASE-10289:
------------------------------------

Hi [~stack],
I am new in this area as well...:-)
my 2 cents:
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..

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. 

3) to avoid port conflict, we do need to try to eliminate random ports as we 
did in this jira. from a long term perspective, I am not sure if we need port 
management at multi-component level...? (e.g. I see a worldwide level port 
registration and management: 
http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?&page=132)

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




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

Reply via email to