[
https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010963#comment-14010963
]
Qiang Tian commented on HBASE-10289:
------------------------------------
Hi guys,
sorry for late response.
the new patch just uploaded is a pluggable solution based on coprocessor, so
that user could turn off or switch back easily.
1)support password authentication
2)support a subset of SSL(Enforcing SSL for communication
) with default configuration. see
http://ddweerasiri.blogspot.com/2011/08/ssl-enabled-jconsole-to-monitor-wso2.html
for example.
3)registry port and connector port can be configured separately. or combined
into 1 when SSL is not enabled. (If SSL is enabled, the connector port must use
a different value than registry port)
4)only load coprocessor for regionserver, since "master is also a regionserver"
in 0.99.
5)the code references the example on official site:
http://docs.oracle.com/javase/7/docs/technotes/guides/management/agent.html
(see section "Example of Mimicking Out-of-the-Box Management")
6)password authentication and SSL test are done manually since the code almost
does nothing for it - most work is related to environment
7)confirmed random port issue is not resolved in JDK 7 unless bug 8035404 is
fixed.
appreciate your comments.
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
> Assignee: Qiang Tian
> 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,
> HBase10289-master.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)
