[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14038537#comment-14038537 ] Hudson commented on HBASE-10289: FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #330 (See [https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/330/]) HBASE-10289 Avoid random port usage by default JMX Server. Create Custom JMX server (Qiang Tian) (apurtell: rev 8ac95e73aeb76bf6bc0679122c772ce093be2955) * hbase-server/src/main/java/org/apache/hadoop/hbase/JMXListener.java * hbase-server/src/test/java/org/apache/hadoop/hbase/TestJMXListener.java * conf/hbase-env.sh 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, 0.98.4 Attachments: HBASE-10289-v4.patch, HBASE-10289.patch, HBASE-10289_1.patch, HBASE-10289_2.patch, HBASE-10289_3.patch, HBase10289-master.patch, hbase10289-0.98.patch, hbase10289-doc_update-master.patch, hbase10289-master-v1.patch, hbase10289-master-v2.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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14037487#comment-14037487 ] Andrew Purtell commented on HBASE-10289: bq. Andrew Purtell when you get a chance, do you want to pull this in sir? Ok. I have a stack of HBase related things to do today, will add this to it. 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, hbase10289-0.98.patch, hbase10289-doc_update-master.patch, hbase10289-master-v1.patch, hbase10289-master-v2.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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14038153#comment-14038153 ] Hudson commented on HBASE-10289: SUCCESS: Integrated in HBase-TRUNK #5220 (See [https://builds.apache.org/job/HBase-TRUNK/5220/]) HBASE-10289 Avoid random port usage by default JMX Server. Create Custome JMX server (Qiang Tian). DOC ADDENDUM (stack: rev b16e36a5b2650b2ce2c7686c6653c77074481115) * src/main/docbkx/configuration.xml 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, hbase10289-0.98.patch, hbase10289-doc_update-master.patch, hbase10289-master-v1.patch, hbase10289-master-v2.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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14038314#comment-14038314 ] Hudson commented on HBASE-10289: SUCCESS: Integrated in HBase-0.98 #348 (See [https://builds.apache.org/job/HBase-0.98/348/]) HBASE-10289 Avoid random port usage by default JMX Server. Create Custom JMX server (Qiang Tian) (apurtell: rev 8ac95e73aeb76bf6bc0679122c772ce093be2955) * conf/hbase-env.sh * hbase-server/src/main/java/org/apache/hadoop/hbase/JMXListener.java * hbase-server/src/test/java/org/apache/hadoop/hbase/TestJMXListener.java 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, 0.98.4 Attachments: HBASE-10289-v4.patch, HBASE-10289.patch, HBASE-10289_1.patch, HBASE-10289_2.patch, HBASE-10289_3.patch, HBase10289-master.patch, hbase10289-0.98.patch, hbase10289-doc_update-master.patch, hbase10289-master-v1.patch, hbase10289-master-v2.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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14034749#comment-14034749 ] Qiang Tian commented on HBASE-10289: Hi [~stack], [~apurtell], could you please take a look at the patch? 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, hbase10289-0.98.patch, hbase10289-doc_update-master.patch, hbase10289-master-v1.patch, hbase10289-master-v2.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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14034775#comment-14034775 ] stack commented on HBASE-10289: --- [~tianq] Sorry about that. I just added the doc addendum to trunk. [~apurtell] when you get a chance, do you want to pull this in sir? 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, hbase10289-0.98.patch, hbase10289-doc_update-master.patch, hbase10289-master-v1.patch, hbase10289-master-v2.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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017819#comment-14017819 ] stack commented on HBASE-10289: --- [~tianq] Mind making a distinct addendum for trunk that has in it only the doc edit Andy suggest? 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, hbase10289-master-v1.patch, hbase10289-master-v2.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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[
https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14018433#comment-14018433
]
Hadoop QA commented on HBASE-10289:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12648419/hbase10289-0.98.patch
against trunk revision .
ATTACHMENT ID: 12648419
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9694//console
This message is automatically generated.
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, hbase10289-0.98.patch,
hbase10289-doc_update-master.patch, hbase10289-master-v1.patch,
hbase10289-master-v2.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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016964#comment-14016964 ] Andrew Purtell commented on HBASE-10289: Sure, I cherry picked the change from trunk and can take it except for the doc update. (We copy docs from trunk into branch releases during the release candidate creation process anyhow.) Let me check that it tests out successfully locally before pushing the merge. 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, hbase10289-master-v1.patch, hbase10289-master-v2.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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016970#comment-14016970 ] Andrew Purtell commented on HBASE-10289: I do recommend a doc update for trunk, if we are still re-using docs from trunk for 0.98 branch. The user will also need to add the JMXListener coprocessor to hbase.coprocessor.master.classes. 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, hbase10289-master-v1.patch, hbase10289-master-v2.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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016977#comment-14016977 ] Demai Ni commented on HBASE-10289: -- [~andrew.purt...@gmail.com], Qiang mentioned offline last night that 0.98 code may be slightly different comparing to trunk, and he is looking into that, and will provide the patch if it is indeed different. He is at another timezone, so I responded for him... Demai 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, hbase10289-master-v1.patch, hbase10289-master-v2.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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016988#comment-14016988 ] Andrew Purtell commented on HBASE-10289: Thanks Demai. 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, hbase10289-master-v1.patch, hbase10289-master-v2.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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14017318#comment-14017318 ] Qiang Tian commented on HBASE-10289: Thanks [~andrew.purt...@gmail.com] [~nidmhbase], I will upload the updated trunk doc and 0.98 patch separately. 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, hbase10289-master-v1.patch, hbase10289-master-v2.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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[
https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015357#comment-14015357
]
Hadoop QA commented on HBASE-10289:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12647886/hbase10289-master-v2.patch
against trunk revision .
ATTACHMENT ID: 12647886
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+# NOTE: HBase provides an alternative JMX implementation to fix the random
ports issue, please see JMX
+
xlink:href=http://docs.oracle.com/javase/6/docs/technotes/guides/management/agent.html;
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/9663//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9663//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9663//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9663//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9663//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9663//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9663//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9663//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9663//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9663//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9663//console
This message is automatically generated.
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, hbase10289-master-v1.patch,
hbase10289-master-v2.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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015735#comment-14015735 ] Hudson commented on HBASE-10289: FAILURE: Integrated in HBase-TRUNK #5166 (See [https://builds.apache.org/job/HBase-TRUNK/5166/]) HBASE-10289 Avoid random port usage by default JMX Server. Create Custome JMX server (Qiang Tian) (stack: rev 80557b872fbf31fec94930fc4723d7a459fe52e7) * hbase-server/src/main/java/org/apache/hadoop/hbase/JMXListener.java * src/main/docbkx/configuration.xml * hbase-server/src/test/java/org/apache/hadoop/hbase/TestJMXListener.java * conf/hbase-env.sh 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, hbase10289-master-v1.patch, hbase10289-master-v2.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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016179#comment-14016179 ] Qiang Tian commented on HBASE-10289: Thanks [~stack]. [~apurtell], would you like it in 0.98? 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, hbase10289-master-v1.patch, hbase10289-master-v2.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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013968#comment-14013968 ] stack commented on HBASE-10289: --- [~tianq] Thank you for the nice patch and excellent doc! Should bin/hbase-env.sh comments be amended around JMX? Does the old way of setting up JMX will work? If so, should the doc mention it as alternative (though refer back to why it is inferior) and should bin/hbase-env.sh comments point into the hbase refguide for an alternative that allows setting explicit, unchanging ports? Nice work [~tianq] 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, hbase10289-master-v1.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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013282#comment-14013282 ] stack commented on HBASE-10289: --- [~tianq] That looks pretty good. At first it looks a bit over the top but it is only ON if you enable it, right? How I enable it? Need a bit of doc or a fat release note. 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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013296#comment-14013296 ] Qiang Tian commented on HBASE-10289: Thanks [~stack], Yes. it is OFF if user does not configure it in hbase-site.xml. (current JMX configuration in hbase-env.sh is also OFF by default) What about adding a JMX part in hbase book section 2.5.3. Other Configurations? e.g. the description of the problem, examples for supported configurations etc. 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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013314#comment-14013314 ] Qiang Tian commented on HBASE-10289: ps making it coprocessor based just utilized the strength of class instantiation of the coprocessor framework, without any other costs. so that we have a real pluggability without modifying other code..(since I thought the native JDK solution is still the best after the bug is fixed)... but if you guys think the original way is better, I can change it back.. 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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[
https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011015#comment-14011015
]
Hadoop QA commented on HBASE-10289:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12647089/HBase10289-master.patch
against trunk revision .
ATTACHMENT ID: 12647089
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 1
warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:red}-1 release audit{color}. The applied patch generated 31 release
audit warnings (more than the trunk's current 0 warnings).
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/9620//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9620//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9620//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9620//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9620//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9620//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9620//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9620//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9620//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9620//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9620//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9620//console
This message is automatically generated.
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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13979398#comment-13979398 ] Qiang Tian commented on HBASE-10289: hi [~nijel], /proc/sys/net/ipv4/ip_local_port_range looks not good solution as it limits port resource. I just happen to find when com.sun.management.jmxremote.local.only=false is set, there is only 1 random port, i.e.: export HBASE_MASTER_OPTS=$HBASE_JMX_BASE -Dcom.sun.management.jmxremote.port=61100 -Dcom.sun.management .jmxremote.local.only=false without com.sun.management.jmxremote.local.only=false: [root@test tmp]# netstat -nltp |grep 61100 tcp0 0 :::61100:::* LISTEN 1989249/java [root@test tmp]# netstat -nltp |grep 1989249 tcp0 0 :::61100:::* LISTEN 1989249/java tcp0 0 :::4159 :::* LISTEN 1989249/java tcp0 0 :::9.181.64.235:6 :::* LISTEN 1989249/java tcp0 0 :::61320:::* LISTEN 1989249/java tcp0 0 :::60010:::* LISTEN 1989249/java with com.sun.management.jmxremote.local.only=false [root@test tmp]# netstat -nltp |grep 61100 tcp0 0 :::61100:::* LISTEN 2021776/java [root@test tmp]# netstat -nltp |grep 2021776 tcp0 0 :::61100:::* LISTEN 2021776/java tcp0 0 :::2174 :::* LISTEN 2021776/java tcp0 0 :::9.181.64.235:6 :::* LISTEN 2021776/java tcp0 0 :::60010:::* LISTEN 2021776/java I tried jconsole can work locally and remotely. could you also have a try? ps below is the description: http://www.oracle.com/technetwork/java/javase/compatibility-417013.html Area: JMX Synopsis: New Property for JMX RMI Connector Server Description: The new property, com.sun.management.jmxremote.local.only, when true (the default) indicates that the local JMX RMI connector will only accept connection requests from local interfaces. Setting this property to false restores JDK 6 behavior, but is not recommended because the local JMX RMI connector server will accept connection requests from both local and remote interfaces. For remote management, the remote JMX RMI connector server should be used with authentication and SLL/TLS encyrption enabled. Nature of Incompatibility: behavioral Regarding to the RMI server port, we could: a)using parameter com.sun.management.jmxremote.rmi.port after upgrade to jdk7. this is the simplest way. b)using existing artifcat catalina-jmx-remote.jar c)implement by ourselves as you mentioned. 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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13979408#comment-13979408 ] Qiang Tian commented on HBASE-10289: ps the official description is talking about JDK7, but I use jdk 6. and in jre/lib/management/management.properties file, there is similar description in RMI connector settings for local management section. 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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13978028#comment-13978028 ] Qiang Tian commented on HBASE-10289: Hi Demai Ni, stack, I took a look. below is the details. the problem is JMX created 2 additional random ports besides the port specified by com.sun.management.jmxremote.port. One port is RMI server port, the other is used by Java Attach API for local attach purpose(see more details below) it looks it has been the case for long time. prior effort focused on customizing the RMI server port, because the port is used by client -- when firewall is configured, client just cannot connect to JMX, for example: http://olegz.wordpress.com/2009/03/23/jmx-connectivity-through-the-firewall/ there is some artifcat to address it as well, e.g. : http://tomcat.apache.org/tomcat-7.0-doc/config/listeners.html#JMX_Remote_Lifecycle_Listener_-_org.apache.catalina.mbeans.JmxRemoteLifecycleListener both registry port(rmiRegistryPortPlatform) and RMI server port(rmiServerPortPlatform) can be configured, and authentication is supported. Sun JDK realized this problem, the RMI server port can be configured via com.sun.management.jmxremote.rmi.port, since JDK7u4. then what about the local attach port, which is also random? According to http://stackoverflow.com/questions/20884353/why-java-opens-3-ports-when-jmx-is-configured, this feature can be disabled by -XX:+DisableAttachMechanism (there is no clear description about it in official link http://docs.oracle.com/javase/7/docs/technotes/tools/windows/java.html), but the guy tested it just does not work, and recently he opened defect against java: http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8035404 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-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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13978569#comment-13978569 ] stack commented on HBASE-10289: --- Thanks [~tianq] Nice write up. RMI is madness yes. So you would suggest we disable our hbase-env.sh configurations and instead go w/ this patch? The local attach port will or will not still be available? 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 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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[
https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960426#comment-13960426
]
Demai Ni commented on HBASE-10289:
--
[~saint@gmail.com], the patch looks good to me.
I configured hbase-site.xml by adding :
{code}
property
namehbase.master.rmi.registry.port/name
value2356/value
/property
property
namehbase.regionserver.rmi.registry.port/name
value2357/value
/property
{code}
and both ports are set on my single-node cluster.
the patch is out of date, I will upload a new one shortly
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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[
https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960552#comment-13960552
]
Hadoop QA commented on HBASE-10289:
---
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12638768/HBASE-10289-v4.patch
against trunk revision .
ATTACHMENT ID: 12638768
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified tests.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/9202//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9202//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9202//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9202//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9202//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9202//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9202//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9202//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9202//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/9202//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/9202//console
This message is automatically generated.
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-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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[
https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960641#comment-13960641
]
stack commented on HBASE-10289:
---
Patch is great. Thanks for testing [~nidmhbase]. How does this patch relate
to the stuff that is in hbase-env.sh?
{code}
# Uncomment and adjust to enable JMX exporting
# See jmxremote.password and jmxremote.access in $JRE_HOME/lib/management to
configure remote password access.
# More details at:
http://java.sun.com/javase/6/docs/technotes/guides/management/agent.html
#
# export HBASE_JMX_BASE=-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
...
{code}
Should we remove hbase-env.sh stuff?
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-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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[
https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13960800#comment-13960800
]
Demai Ni commented on HBASE-10289:
--
[~stack], thanks for reviewing the patch.
I am not familiar with JMX setting. from my cluster:
{code}
export HBASE_JMX_BASE=-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=true
-Dcom.sun.management.jmxremote.password.file=/opt/ibm/biginsights/conf/jmx/hbase/jmxremote.password
-Dcom.sun.management.jmxremote.access.file=/opt/ibm/biginsights/conf/jmx/hbase/jmxremote.access
{code}
the value $HBASE_JMX_BASE is used to start others, like HMaster, TaskTracker.
Probably won't hurt to leave it there... Again, I am not familiar with
that(smile)
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-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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13959201#comment-13959201 ] Demai Ni commented on HBASE-10289: -- [~nijel]. just like to check the status of this jira. We encounter a similar problem on 96.0. thanks for the fix 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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13959418#comment-13959418 ] Demai Ni commented on HBASE-10289: -- [~saint@gmail.com], I haven't tried the patch yet. the problem on my end was reported by a co-work, and be able to set the port will resolve the issue. I will try out the patch on my cluster tomorrow. 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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[
https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13885142#comment-13885142
]
Hadoop QA commented on HBASE-10289:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12625812/HBASE-10289_2.patch
against trunk revision .
ATTACHMENT ID: 12625812
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop1.1{color}. The patch compiles against the hadoop
1.1 profile.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 2
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.TestCheckTestClasses
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/8550//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8550//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8550//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8550//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8550//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8550//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8550//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8550//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8550//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8550//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/8550//console
This message is automatically generated.
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
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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[
https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13885349#comment-13885349
]
Hadoop QA commented on HBASE-10289:
---
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12625852/HBASE-10289_3.patch
against trunk revision .
ATTACHMENT ID: 12625852
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop1.1{color}. The patch compiles against the hadoop
1.1 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/8551//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8551//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8551//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8551//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8551//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8551//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8551//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8551//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8551//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8551//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/8551//console
This message is automatically generated.
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.1.5#6160)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[
https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13885035#comment-13885035
]
Hadoop QA commented on HBASE-10289:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12625251/HBASE-10289_1.patch
against trunk revision .
ATTACHMENT ID: 12625251
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:red}-1 hadoop1.0{color}. The patch failed to compile against the
hadoop 1.0 profile.
Here is snippet of errors:
{code}[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile)
on project hbase-server: Compilation failure: Compilation failure:
[ERROR]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java:[243,34]
package org.apache.hadoop.hbase.jmx does not exist
[ERROR]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java:[524,10]
cannot find symbol
[ERROR] symbol : class JMXServer
[ERROR] location: class org.apache.hadoop.hbase.regionserver.HRegionServer
[ERROR]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMasterCommandLine.java:[44,34]
package org.apache.hadoop.hbase.jmx does not exist
--
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile)
on project hbase-server: Compilation failure
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
--
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation
failure
at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:729)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more{code}
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/8548//console
This message is automatically generated.
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
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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13885061#comment-13885061 ] stack commented on HBASE-10289: --- Please follow the coding convention you find in the rest of the file -- two spaces for tabs and the way we do catch clauses, etc. NIce test. Did you forget to add JMXServer? 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 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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13885106#comment-13885106 ] nijel commented on HBASE-10289: --- yes.. i missed the file.. added now made changes in test file to get compile with Hadoop 1.x also 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 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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13875000#comment-13875000 ] nijel commented on HBASE-10289: --- can we remove the talk in hbase-env.sh of flags for starting JMX? 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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13875024#comment-13875024 ] nijel commented on HBASE-10289: --- pls ignore previous comment.. bq. Tell me more nijel In hbase-env.sh in trunk you can specify ports for JMX (IIRC). - Even if we specify the port one of the port will be random. bq. can we remove the talk in hbase-env.sh of flags for starting JMX? - Yes. After this patch we need not specify the flags in hbase-env.sh bq. What happens if someone passes the flags? Will we have two JMX servers running? - Yes, 2 JMX servers will be running. In both the servers beans will be registered. The idea behind this patch is to give a option to user to control the ports used by JMX server. 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)
[jira] [Commented] (HBASE-10289) Avoid random port usage by default JMX Server. Create Custome JMX server
[ https://issues.apache.org/jira/browse/HBASE-10289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13875053#comment-13875053 ] stack commented on HBASE-10289: --- bq. The idea behind this patch is to give a option to user to control the ports used by JMX server. Great. These defines are only used in one place so I'd move them there rather than add them to HConstants: + /** Configuration key for rmi registry port */ + public static final String RMI_REGISTRY_PORT = .rmi.registry.port; + + /** Configuration key for rmi connector port */ + public static final String RMI_CONNECTOR_PORT = .rmi.connector.port; + + /** Configuration key for rmi registry ip */ + public static final String RMI_REGISTRY_IP = .rmi.registry.ip; + + /** Configuration key for rmi connector name */ + public static final String RMI_REGISTRY_CONNECTORNAME = .rmi.registry.connectorname; + + /** Default rmi registry ip value */ + public static final String RMI_REGISTRY_IP_DEFAULT = 127.0.0.1; JMXServer is missing an apache license (see adjacent .java files for how). I can add the audience annotation on commit. Class could do with a comment -- a synopsis of the comments you made above explaining this feature to me would do nicely. How does your server get started and shutdown? It should be embedded in Master and RegionServer? 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)
