[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471081#comment-16471081 ] Hadoop QA commented on ZOOKEEPER-1971: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12828907/ZOOKEEPER-1971-03.patch against trunk revision 2fa315b7d0ed65828479fcdcc9e76ca8552fba4a. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 2 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 3.0.1) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3671//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3671//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3671//console This message is automatically generated. > Make JMX remote monitoring port configurable > > > Key: ZOOKEEPER-1971 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.5.0 > Environment: All >Reporter: Biju Nair >Assignee: Mohammad Arshad >Priority: Major > Fix For: 3.6.0, 3.5.5 > > Attachments: GeneratedDoc-ZOOKEEPER-1971-03.pdf, > ZOOKEEPER-1971-01.patch, ZOOKEEPER-1971-02.patch, ZOOKEEPER-1971-03.patch, > zookeeperAdmin.pdf, zookeeperJMX.pdf > > > This is a follow-up item from ZOOKEEPER-1948. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225384#comment-16225384 ] Nicolas Carlier commented on ZOOKEEPER-1971: Any update on this ticket. Version 3.4 is also affected. > Make JMX remote monitoring port configurable > > > Key: ZOOKEEPER-1971 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.5.0 > Environment: All >Reporter: Biju Nair >Assignee: Mohammad Arshad > Fix For: 3.5.4, 3.6.0 > > Attachments: GeneratedDoc-ZOOKEEPER-1971-03.pdf, > ZOOKEEPER-1971-01.patch, ZOOKEEPER-1971-02.patch, ZOOKEEPER-1971-03.patch, > zookeeperAdmin.pdf, zookeeperJMX.pdf > > > This is a follow-up item from ZOOKEEPER-1948. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15498247#comment-15498247 ] Arshad Mohammad commented on ZOOKEEPER-1971: ZOOKEEPER-1971-03.patch addressed all review comments, also did some more changes to improve the overall patch. > Make JMX remote monitoring port configurable > > > Key: ZOOKEEPER-1971 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.5.0 > Environment: All >Reporter: Biju Nair >Assignee: Arshad Mohammad > Fix For: 3.5.3, 3.6.0 > > Attachments: GeneratedDoc-ZOOKEEPER-1971-03.pdf, > ZOOKEEPER-1971-01.patch, ZOOKEEPER-1971-02.patch, ZOOKEEPER-1971-03.patch, > zookeeperAdmin.pdf, zookeeperJMX.pdf > > > This is a follow-up item from ZOOKEEPER-1948. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15498241#comment-15498241 ] Arshad Mohammad commented on ZOOKEEPER-1971: There is no test failure. One test case skipped but not because of this patch > Make JMX remote monitoring port configurable > > > Key: ZOOKEEPER-1971 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.5.0 > Environment: All >Reporter: Biju Nair >Assignee: Arshad Mohammad > Fix For: 3.5.3, 3.6.0 > > Attachments: GeneratedDoc-ZOOKEEPER-1971-03.pdf, > ZOOKEEPER-1971-01.patch, ZOOKEEPER-1971-02.patch, ZOOKEEPER-1971-03.patch, > zookeeperAdmin.pdf, zookeeperJMX.pdf > > > This is a follow-up item from ZOOKEEPER-1948. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15497470#comment-15497470 ] Hadoop QA commented on ZOOKEEPER-1971: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12828907/ZOOKEEPER-1971-03.patch against trunk revision b2a484cfe743116d2531fe5d1e1d78b3960c511e. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 2 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3438//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3438//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3438//console This message is automatically generated. > Make JMX remote monitoring port configurable > > > Key: ZOOKEEPER-1971 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.5.0 > Environment: All >Reporter: Biju Nair >Assignee: Arshad Mohammad > Fix For: 3.5.3, 3.6.0 > > Attachments: GeneratedDoc-ZOOKEEPER-1971-03.pdf, > ZOOKEEPER-1971-01.patch, ZOOKEEPER-1971-02.patch, ZOOKEEPER-1971-03.patch, > zookeeperAdmin.pdf, zookeeperJMX.pdf > > > This is a follow-up item from ZOOKEEPER-1948. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15497358#comment-15497358 ] Hadoop QA commented on ZOOKEEPER-1971: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12828895/ZOOKEEPER-1971-03.patch against trunk revision b2a484cfe743116d2531fe5d1e1d78b3960c511e. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 2 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3436//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3436//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3436//console This message is automatically generated. > Make JMX remote monitoring port configurable > > > Key: ZOOKEEPER-1971 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.5.0 > Environment: All >Reporter: Biju Nair >Assignee: Arshad Mohammad > Fix For: 3.5.3, 3.6.0 > > Attachments: GeneratedDoc-ZOOKEEPER-1971-03.pdf, > ZOOKEEPER-1971-01.patch, ZOOKEEPER-1971-02.patch, zookeeperAdmin.pdf, > zookeeperJMX.pdf > > > This is a follow-up item from ZOOKEEPER-1948. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15497350#comment-15497350 ] Hadoop QA commented on ZOOKEEPER-1971: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12828900/GeneratedDoc-ZOOKEEPER-1971-03.pdf against trunk revision b2a484cfe743116d2531fe5d1e1d78b3960c511e. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3437//console This message is automatically generated. > Make JMX remote monitoring port configurable > > > Key: ZOOKEEPER-1971 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.5.0 > Environment: All >Reporter: Biju Nair >Assignee: Arshad Mohammad > Fix For: 3.5.3, 3.6.0 > > Attachments: GeneratedDoc-ZOOKEEPER-1971-03.pdf, > ZOOKEEPER-1971-01.patch, ZOOKEEPER-1971-02.patch, ZOOKEEPER-1971-03.patch, > zookeeperAdmin.pdf, zookeeperJMX.pdf > > > This is a follow-up item from ZOOKEEPER-1948. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491433#comment-15491433 ] Arshad Mohammad commented on ZOOKEEPER-1971: If we throw exception many exiting zookeeper applications start failing because of port conflict. Exception was not thrown to make the existing applications work as before. But there are many other problem with this approach even the normal jmx env is not started. I will disable custom jxm by default in the code, but enable custom jmx from zkServer.sh by default then we can throw exception in case of the custom jxm env fails. I will update the patch for this. > Make JMX remote monitoring port configurable > > > Key: ZOOKEEPER-1971 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.5.0 > Environment: All >Reporter: Biju Nair >Assignee: Arshad Mohammad > Fix For: 3.5.3, 3.6.0 > > Attachments: ZOOKEEPER-1971-01.patch, ZOOKEEPER-1971-02.patch, > zookeeperAdmin.pdf, zookeeperJMX.pdf > > > This is a follow-up item from ZOOKEEPER-1948. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491361#comment-15491361 ] Hadoop QA commented on ZOOKEEPER-1971: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12828524/ZOOKEEPER-1971-02.patch against trunk revision b2a484cfe743116d2531fe5d1e1d78b3960c511e. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3431//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3431//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3431//console This message is automatically generated. > Make JMX remote monitoring port configurable > > > Key: ZOOKEEPER-1971 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.5.0 > Environment: All >Reporter: Biju Nair >Assignee: Arshad Mohammad > Fix For: 3.5.3, 3.6.0 > > Attachments: ZOOKEEPER-1971-01.patch, ZOOKEEPER-1971-02.patch, > zookeeperAdmin.pdf, zookeeperJMX.pdf > > > This is a follow-up item from ZOOKEEPER-1948. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491319#comment-15491319
]
Arshad Mohammad commented on ZOOKEEPER-1971:
Thanks [~phunt] for the feedback
There is two reasons current patch is not working with JMXSSL=true
1)There is a problem in the code
2) Some more configurations are required,in addition to what you already
configured.
Submitting new patch to fix the 1) problem.
After this new patch following configurations worked for me.
{noformat}
configured rmi.connector.port=6615 in zoo.cfg
added following in zkEnv.sh
SERVER_JVMFLAGS="$SERVER_JVMFLAGS
-Djavax.net.ssl.keyStore=/home/sage/resources/common/keystore"
SERVER_JVMFLAGS="$SERVER_JVMFLAGS -Djavax.net.ssl.keyStorePassword=mypass"
SERVER_JVMFLAGS="$SERVER_JVMFLAGS
-Djavax.net.ssl.trustStore=/home/sage/resources/common/keystore"
SERVER_JVMFLAGS="$SERVER_JVMFLAGS -Djavax.net.ssl.trustStorePassword=mypass"
export SERVER_JVMFLAGS=$SERVER_JVMFLAGS
export JMXSSL=true
export JMXPORT="6610"
Connected from JConsole:
jconsole -J-Djavax.net.ssl.trustStore=D:/workspace/ssl/keystore
-J-Djavax.net.ssl.trustStorePassword=mypass
{noformat}
> Make JMX remote monitoring port configurable
>
>
> Key: ZOOKEEPER-1971
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
>Affects Versions: 3.5.0
> Environment: All
>Reporter: Biju Nair
>Assignee: Arshad Mohammad
> Fix For: 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-1971-01.patch, zookeeperAdmin.pdf,
> zookeeperJMX.pdf
>
>
> This is a follow-up item from ZOOKEEPER-1948.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475151#comment-15475151 ] Patrick Hunt commented on ZOOKEEPER-1971: - One other thing I noticed - if JMX fails to start (e.g. my previous comment) the ZK server stays running, it doesn't exit. Is this the behavior we want? If the user is requesting JMX and it fails to come up, shouldn't we be exiting? > Make JMX remote monitoring port configurable > > > Key: ZOOKEEPER-1971 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.5.0 > Environment: All >Reporter: Biju Nair >Assignee: Arshad Mohammad > Fix For: 3.5.3, 3.6.0 > > Attachments: ZOOKEEPER-1971-01.patch, zookeeperAdmin.pdf, > zookeeperJMX.pdf > > > This is a follow-up item from ZOOKEEPER-1948. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475145#comment-15475145
]
Patrick Hunt commented on ZOOKEEPER-1971:
-
[~arshad.mohammad] - this looks great, however when I tried it out I ran into
an issue. Perhaps I'm doing it wrong, can you provide insight?
I added this to zoo.cfg
rmi.registry.port=12101
rmi.connector.port=12102
When I start the zk server I can connect to it just fine using jconsole (this
is all on localhost, no remote)
However if I run the service with
JMXSSL=true bin/zkServer.sh start
I see the following in the log
{noformat}
2016-09-08 14:51:27,773 [myid:] - INFO [main:MBeanRegistry@77] - JMX is
enabled, starting Custom JMX environment.
2016-09-08 14:51:27,774 [myid:] - INFO [main:JMXEnvService@174] -
zookeeper.rmi.registry.port configured value is 12101.
2016-09-08 14:51:27,774 [myid:] - INFO [main:JMXEnvService@174] -
zookeeper.rmi.connector.port configured value is 12102.
2016-09-08 14:51:27,774 [myid:] - INFO [main:JMXEnvService@103] -
rmiSSL:true,authenticate:false,passwordFile:null,accessFile:null
2016-09-08 14:51:27,952 [myid:] - INFO [main:JMXEnvService@79] -
service:jmx:rmi://127.0.0.1:12102/jndi/rmi://127.0.0.1:12101/jmxrmi
2016-09-08 14:51:28,133 [myid:] - ERROR [main:MBeanRegistry@84] - Failed to
start the custom JMX environment.
java.io.IOException: Cannot bind to URL [rmi://127.0.0.1:12101/jmxrmi]:
javax.naming.CommunicationException [Root exception is
java.rmi.ConnectIOException: non-JRMP server at remote endpoint]
at
javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:827)
at
javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:432)
at
org.apache.zookeeper.jmx.JMXEnvService.startConnectorServer(JMXEnvService.java:149)
at org.apache.zookeeper.jmx.JMXEnvService.start(JMXEnvService.java:162)
at org.apache.zookeeper.jmx.MBeanRegistry.(MBeanRegistry.java:80)
at
org.apache.zookeeper.jmx.MBeanRegistry.(MBeanRegistry.java:48)
at
org.apache.zookeeper.server.ZooKeeperServer.registerJMX(ZooKeeperServer.java:417)
at
org.apache.zookeeper.server.ZooKeeperServer.startup(ZooKeeperServer.java:450)
at
org.apache.zookeeper.server.NIOServerCnxnFactory.startup(NIOServerCnxnFactory.java:765)
at
org.apache.zookeeper.server.ServerCnxnFactory.startup(ServerCnxnFactory.java:98)
at
org.apache.zookeeper.server.ZooKeeperServerMain.runFromConfig(ZooKeeperServerMain.java:140)
at
org.apache.zookeeper.server.ZooKeeperServerMain.initializeAndRun(ZooKeeperServerMain.java:104)
at
org.apache.zookeeper.server.ZooKeeperServerMain.main(ZooKeeperServerMain.java:62)
at
org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:125)
at
org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:79)
Caused by: javax.naming.CommunicationException [Root exception is
java.rmi.ConnectIOException: non-JRMP server at remote endpoint]
at
com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:147)
at
com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:228)
at javax.naming.InitialContext.bind(InitialContext.java:425)
at
javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:644)
at
javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
... 13 more
Caused by: java.rmi.ConnectIOException: non-JRMP server at remote endpoint
at
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:248)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:342)
at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
at
com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:141)
... 17 more
2016-09-08 14:51:28,139 [myid:] - INFO [main:ContainerManager@64] - Using
checkIntervalMs=6 maxPerMinute=1
{noformat}
Note that I am on a mac using
java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)
> Make JMX remote monitoring port configurable
>
>
> Key: ZOOKEEPER-1971
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
>Affects Versions: 3.5.0
> Environment: All
>Reporter: Biju Nair
>Assignee: Arshad Mohammad
> Fix For: 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-1971-01.patch, zookeeperAdmin.pdf,
> zookeeperJMX.pdf
>
>
> This is a follow-up item from
[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415652#comment-15415652 ] Hadoop QA commented on ZOOKEEPER-1971: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12823101/zookeeperJMX.pdf against trunk revision 1755786. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3352//console This message is automatically generated. > Make JMX remote monitoring port configurable > > > Key: ZOOKEEPER-1971 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.5.0 > Environment: All >Reporter: Biju Nair >Assignee: Arshad Mohammad > Fix For: 3.5.3 > > Attachments: ZOOKEEPER-1971-01.patch, zookeeperAdmin.pdf, > zookeeperJMX.pdf > > > This is a follow-up item from ZOOKEEPER-1948. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415648#comment-15415648 ] Arshad Mohammad commented on ZOOKEEPER-1971: attached generated doc zookeeperAdmin.pdf and zookeeperJMX.pdf Plese refer "2.10.5. ZooKeeper JMX Configuration" in zookeeperAdmin.pdf for newly added configuration details. Hope these document help in reviews > Make JMX remote monitoring port configurable > > > Key: ZOOKEEPER-1971 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.5.0 > Environment: All >Reporter: Biju Nair >Assignee: Arshad Mohammad > Fix For: 3.5.3 > > Attachments: ZOOKEEPER-1971-01.patch, zookeeperAdmin.pdf, > zookeeperJMX.pdf > > > This is a follow-up item from ZOOKEEPER-1948. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415465#comment-15415465 ] Hadoop QA commented on ZOOKEEPER-1971: -- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12823065/ZOOKEEPER-1971-01.patch against trunk revision 1755379. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3348//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3348//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3348//console This message is automatically generated. > Make JMX remote monitoring port configurable > > > Key: ZOOKEEPER-1971 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971 > Project: ZooKeeper > Issue Type: Improvement > Components: server >Affects Versions: 3.5.0 > Environment: All >Reporter: Biju Nair >Assignee: Arshad Mohammad > Fix For: 3.5.3 > > Attachments: ZOOKEEPER-1971-01.patch > > > This is a follow-up item from ZOOKEEPER-1948. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415420#comment-15415420 ] Arshad Mohammad commented on ZOOKEEPER-1971: HBASE-10289 has created Custom JMX server to get rid of two extra ports. We also can do the same thing here. Submitting the fix ZOOKEEPER-1971-01.patch > Make JMX remote monitoring port configurable > > > Key: ZOOKEEPER-1971 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971 > Project: ZooKeeper > Issue Type: Improvement > Components: server > Environment: All >Reporter: Biju Nair >Assignee: Arshad Mohammad > Attachments: ZOOKEEPER-1971-01.patch > > > This is a follow-up item from ZOOKEEPER-1948. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15003900#comment-15003900 ] Arshad Mohammad commented on ZOOKEEPER-1971: After adding -Dcom.sun.management.jmxremote.rmi.port=$JMXPORT, now there is only one extra port and as per information at [stackoverflow thread| http://stackoverflow.com/questions/20884353/why-java-opens-3-ports-when-jmx-is-configured]. this can not be configured. So there will be at least one radom port > Make JMX remote monitoring port configurable > > > Key: ZOOKEEPER-1971 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971 > Project: ZooKeeper > Issue Type: Improvement > Components: server > Environment: All >Reporter: Biju Nair >Assignee: Arshad Mohammad > > This is a follow-up item from ZOOKEEPER-1948. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15003861#comment-15003861
]
Arshad Mohammad commented on ZOOKEEPER-1971:
When jmx is enabled, it opens total three ports(two extra ports),
*When JMX enabled and JMX configured port is 9090*
*netstat -nap | grep pid result:*
{noformat}
tcp0 0 0.0.0.0:44460.0.0.0:* LISTEN
14898/java --debug
tcp0 0 :::58702:::*LISTEN
14898/java --THIS IS EXTRA PORT
tcp0 0 127.0.0.1:3890 :::*LISTEN
14898/java --leader election port
tcp0 0 :::62899:::*LISTEN
14898/java --THIS IS EXTRA PORT
tcp0 0 :::8090 :::*LISTEN
14898/java -- admin port
tcp0 0 :::9090 :::*LISTEN
14898/java --THIS IS CONFIGURED JMX PORT
tcp0 0 :::2183 :::*LISTEN
14898/java --client port
tcp0 0 127.0.0.1:2890 :::*LISTEN
21284/java --quorum peer port
{noformat}
*When JMX disabled by adding export JMXDISABLE=true in zkEnv.sh*
*netstat -nap | grep pid result:*
{noformat}
tcp0 0 0.0.0.0:44460.0.0.0:* LISTEN
21284/java
tcp0 0 127.0.0.1:3890 :::*LISTEN
21284/java
tcp0 0 :::8090 :::*LISTEN
21284/java
tcp0 0 :::2183 :::*LISTEN
21284/java
tcp0 0 127.0.0.1:2890 :::*LISTEN
21284/java
{noformat}
There is no extra port in this case
> Make JMX remote monitoring port configurable
>
>
> Key: ZOOKEEPER-1971
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Environment: All
>Reporter: Biju Nair
>Assignee: Arshad Mohammad
>
> This is a follow-up item from ZOOKEEPER-1948.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14996674#comment-14996674
]
Arshad Mohammad commented on ZOOKEEPER-1971:
JMX port is already configurable through JMXPORT environment variable. If user
adds {{export JMXPORT="9090"}} in {{zkEnv.sh}} or {{zookeeper-env.sh}} then
jmx will start on port 9090.
So there is nothing to be done as part of this JIRA. I will soon close this
JIRA.
> Make JMX remote monitoring port configurable
>
>
> Key: ZOOKEEPER-1971
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Environment: All
>Reporter: Biju Nair
>Assignee: Arshad Mohammad
>
> This is a follow-up item from ZOOKEEPER-1948.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14996714#comment-14996714 ] nijel commented on ZOOKEEPER-1971: -- Hi [~arshad.mohammad] thanks for the analysis As per my initial analysis, only one jmx port can be configurable, where as when JMX is enabled it is listening to 2 ports will be open for listening Normally in production clusters, listening to a non-configured port is not recommandable. > Make JMX remote monitoring port configurable > > > Key: ZOOKEEPER-1971 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971 > Project: ZooKeeper > Issue Type: Improvement > Components: server > Environment: All >Reporter: Biju Nair >Assignee: Arshad Mohammad > > This is a follow-up item from ZOOKEEPER-1948. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1971) Make JMX remote monitoring port configurable
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14074227#comment-14074227 ] nijel commented on ZOOKEEPER-1971: -- can i take up this ? Make JMX remote monitoring port configurable Key: ZOOKEEPER-1971 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1971 Project: ZooKeeper Issue Type: Improvement Components: server Environment: All Reporter: Biju Nair This is a follow-up item from ZOOKEEPER-1948. -- This message was sent by Atlassian JIRA (v6.2#6252)
