[jira] [Commented] (ZOOKEEPER-2592) Zookeeper is not recoverable once running system( machine on which zookeeper is running) is out of space
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15663839#comment-15663839 ] Rakesh Kumar Singh commented on ZOOKEEPER-2592: --- This issue is found in 3.5.1 version. As Rakesh R suggested, i will put the patch provided as part of ZOOKEEPER-2247 issue and can try again. But this issue is there in standalone mode. > Zookeeper is not recoverable once running system( machine on which zookeeper > is running) is out of space > > > Key: ZOOKEEPER-2592 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2592 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh >Priority: Critical > > Zookeeper is not recoverable once running system( machine on which zookeeper > is running) is out of space > Steps to reproduce:- > 1. Install zookeeper on standalone mode and start zookeeper > 2. Make the machine physical memory full > 3. Connect through client to zookeeper and trying create some znodes with > some data. > 4. After sometime creating further znode will not happened as complete memory > is occupied > 5. Now start creating space in that machine > 6. Again connect through a client. Connection is fine. Now try to execute any > command like "ls / " it fails even though now space is more than 11gb > Client log:- > BLR107042:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin > # df -h > Filesystem Size Used Avail Use% Mounted on > /dev/xvda2 36G 24G 11G 70% / > udev1.9G 116K 1.9G 1% /dev > tmpfs 1.9G 0 1.9G 0% /dev/shm > BLR107042:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin > # ./zkCli.sh > Connecting to localhost:2181 > 2016-09-19 22:50:20,227 [myid:] - INFO [main:Environment@109] - Client > environment:zookeeper.version=3.5.1-alpha--1, built on 08/18/2016 08:20 GMT > 2016-09-19 22:50:20,231 [myid:] - INFO [main:Environment@109] - Client > environment:host.name=BLR107042 > 2016-09-19 22:50:20,231 [myid:] - INFO [main:Environment@109] - Client > environment:java.version=1.7.0_79 > 2016-09-19 22:50:20,234 [myid:] - INFO [main:Environment@109] - Client > environment:java.vendor=Oracle Corporation > 2016-09-19 22:50:20,234 [myid:] - INFO [main:Environment@109] - Client > environment:java.home=/usr/java/jdk1.7.0_79/jre > 2016-09-19 22:50:20,234 [myid:] - INFO [main:Environment@109] - Client > environment:java.class.path=/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../build/classes:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../build/lib/*.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/slf4j-log4j12-1.7.5.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/slf4j-api-1.7.5.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/servlet-api-2.5-20081211.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/netty-3.7.0.Final.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/log4j-1.2.16.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jline-2.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jetty-util-6.1.26.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jetty-6.1.26.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/javacc.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jackson-mapper-asl-1.9.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jackson-core-asl-1.9.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/commons-cli-1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/ant-eclipse-1.0-jvm1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../zookeeper-3.5.1-alpha.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../src/java/lib/ant-eclipse-1.0-jvm1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../conf:/usr/java/jdk1.7.0_79/lib > 2016-09-19 22:50:20,234 [myid:] - INFO [main:Environment@109] - Client > environment:java.library.path=/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib > 2016-09-19 22:50:20,234 [myid:] - INFO [main:Environment@109] - Client > environment:java.io.tmpdir=/tmp > 2016-09-19 22:50:20,234 [myid:] - INFO [main:Environment@109] - Client > environment:java.compiler= > 2016-09-19 22:50:20,235 [myid:] - INFO [main:Environment@109] - Client > environment:os.name=Linux > 2016-09-19 22:50:20,235 [myid:] - INFO [main:Environment@109] - Client >
[jira] [Assigned] (ZOOKEEPER-2521) space should be truncated while reading password for keystore/truststore which is required to configure while SSL enabled
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh reassigned ZOOKEEPER-2521: - Assignee: (was: Rakesh Kumar Singh) > space should be truncated while reading password for keystore/truststore > which is required to configure while SSL enabled > - > > Key: ZOOKEEPER-2521 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2521 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.5.3, 3.6.0 > > Attachments: ZOOKEEPER-2521.2.patch, ZOOKEEPER-2521.patch > > > space should be truncated while reading password for keystore/truststore > which is required to configure while SSL enabled. > As of now if we configure the password with any heading/trailing space, the > zookeeper server will fail to start. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ZOOKEEPER-2521) space should be truncated while reading password for keystore/truststore which is required to configure while SSL enabled
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh reassigned ZOOKEEPER-2521: - Assignee: Rakesh Kumar Singh > space should be truncated while reading password for keystore/truststore > which is required to configure while SSL enabled > - > > Key: ZOOKEEPER-2521 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2521 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.5.3, 3.6.0 > > Attachments: ZOOKEEPER-2521.2.patch, ZOOKEEPER-2521.patch > > > space should be truncated while reading password for keystore/truststore > which is required to configure while SSL enabled. > As of now if we configure the password with any heading/trailing space, the > zookeeper server will fail to start. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2521) space should be truncated while reading password for keystore/truststore which is required to configure while SSL enabled
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15608053#comment-15608053 ] Rakesh Kumar Singh commented on ZOOKEEPER-2521: --- Should we update the document regarding this..? > space should be truncated while reading password for keystore/truststore > which is required to configure while SSL enabled > - > > Key: ZOOKEEPER-2521 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2521 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.5.3, 3.6.0 > > Attachments: ZOOKEEPER-2521.2.patch, ZOOKEEPER-2521.patch > > > space should be truncated while reading password for keystore/truststore > which is required to configure while SSL enabled. > As of now if we configure the password with any heading/trailing space, the > zookeeper server will fail to start. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2556) peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2556: -- Attachment: ZOOKEEPER-2556.patch > peerType remains as "observer" in zoo.cfg even though we change the node from > observer to participant runtime > - > > Key: ZOOKEEPER-2556 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2556 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > Attachments: ZOOKEEPER-2556.patch, ZOOKEEPER-2556.patch > > > peerType remains as "observer" in zoo.cfg even though we change the node from > observer to participant runtime > Steps to reproduce:- > 1. Start zookeeper in cluster with one node as observer by configuring > peerType=observer in zoo.cfg and server.2=10.18.219.50:2888:3888:observer;2181 > 2. Start the cluster > 3. start a client and change the node from observer to participant, the > configuration related to peertype remained same though other things like > clientport got from zoo.cfg > >reconfig -remove 2 -add 2=10.18.219.50:2888:3888:participant;2181 > We should either remove this parameter or update with correct node type at > run time -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2556) peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15581238#comment-15581238 ] Rakesh Kumar Singh commented on ZOOKEEPER-2556: --- Pls review and commit if looks fine. > peerType remains as "observer" in zoo.cfg even though we change the node from > observer to participant runtime > - > > Key: ZOOKEEPER-2556 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2556 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > Attachments: ZOOKEEPER-2556.patch > > > peerType remains as "observer" in zoo.cfg even though we change the node from > observer to participant runtime > Steps to reproduce:- > 1. Start zookeeper in cluster with one node as observer by configuring > peerType=observer in zoo.cfg and server.2=10.18.219.50:2888:3888:observer;2181 > 2. Start the cluster > 3. start a client and change the node from observer to participant, the > configuration related to peertype remained same though other things like > clientport got from zoo.cfg > >reconfig -remove 2 -add 2=10.18.219.50:2888:3888:participant;2181 > We should either remove this parameter or update with correct node type at > run time -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2467) NullPointerException when redo Command is passed negative value
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15574433#comment-15574433 ] Rakesh Kumar Singh commented on ZOOKEEPER-2467: --- Thanks Rakesh. > NullPointerException when redo Command is passed negative value > --- > > Key: ZOOKEEPER-2467 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2467 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.4.8, 3.5.2 > Environment: Linux , windows >Reporter: Joshi Shankar >Assignee: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.4.10, 3.5.3 > > Attachments: ZOOKEEPER-2467-1.patch, ZOOKEEPER-2467-final.patch, > ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch, > ZOOKEEPER-2467.patch > > > When negative value of argument is passed to redo command . > [zk: localhost:2181(CONNECTED) 0] redo -1 > Exception in thread "main" java.lang.NullPointerException > at java.util.StringTokenizer.(Unknown Source) > at java.util.StringTokenizer.(Unknown Source) > at > org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.parseCommand(ZooKeeperMain.java:227) > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:645) > at > org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:588) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:323) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:282) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2467) NullPointerException when redo Command is passed negative value
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2467: -- Attachment: ZOOKEEPER-2467.patch Uploading patch. Pls review and submit if fine. > NullPointerException when redo Command is passed negative value > --- > > Key: ZOOKEEPER-2467 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2467 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.4.8, 3.5.2 > Environment: Linux , windows >Reporter: Joshi Shankar >Assignee: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.4.10, 3.5.3 > > Attachments: ZOOKEEPER-2467-1.patch, ZOOKEEPER-2467-final.patch, > ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch, > ZOOKEEPER-2467.patch > > > When negative value of argument is passed to redo command . > [zk: localhost:2181(CONNECTED) 0] redo -1 > Exception in thread "main" java.lang.NullPointerException > at java.util.StringTokenizer.(Unknown Source) > at java.util.StringTokenizer.(Unknown Source) > at > org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.parseCommand(ZooKeeperMain.java:227) > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:645) > at > org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:588) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:323) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:282) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2467) NullPointerException when redo Command is passed negative value
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15554216#comment-15554216 ] Rakesh Kumar Singh commented on ZOOKEEPER-2467: --- Hi [~fpj], i have covered 3 suggestions mentioned by you but i think 4th point may not be valid. As redo command is not any specific (separate) command but calling other commands and hence it calls the corresponding exec() implementation and we may not be able to define any sepefic exec() implementation for redo command. Pls input your feedback. Thanks > NullPointerException when redo Command is passed negative value > --- > > Key: ZOOKEEPER-2467 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2467 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.4.8, 3.5.2 > Environment: Linux , windows >Reporter: Joshi Shankar >Assignee: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.4.10, 3.5.3 > > Attachments: ZOOKEEPER-2467-1.patch, ZOOKEEPER-2467-final.patch, > ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch > > > When negative value of argument is passed to redo command . > [zk: localhost:2181(CONNECTED) 0] redo -1 > Exception in thread "main" java.lang.NullPointerException > at java.util.StringTokenizer.(Unknown Source) > at java.util.StringTokenizer.(Unknown Source) > at > org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.parseCommand(ZooKeeperMain.java:227) > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:645) > at > org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:588) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:323) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:282) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2467) NullPointerException when redo Command is passed negative value
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15554209#comment-15554209 ] Rakesh Kumar Singh commented on ZOOKEEPER-2467: --- [~rakeshr] i have covered 3 suggestions mentioned by Flavio Junqueira but i feel 4th point is not valid. As redo command is not any specific (separate) command but calling other commands and hence it calls the corresponding exec() implementation and we may not be able to define any sepefic exec() implementation for redo command. > NullPointerException when redo Command is passed negative value > --- > > Key: ZOOKEEPER-2467 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2467 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.4.8, 3.5.2 > Environment: Linux , windows >Reporter: Joshi Shankar >Assignee: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.4.10, 3.5.3 > > Attachments: ZOOKEEPER-2467-1.patch, ZOOKEEPER-2467-final.patch, > ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch > > > When negative value of argument is passed to redo command . > [zk: localhost:2181(CONNECTED) 0] redo -1 > Exception in thread "main" java.lang.NullPointerException > at java.util.StringTokenizer.(Unknown Source) > at java.util.StringTokenizer.(Unknown Source) > at > org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.parseCommand(ZooKeeperMain.java:227) > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:645) > at > org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:588) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:323) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:282) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2467) NullPointerException when redo Command is passed negative value
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551805#comment-15551805 ] Rakesh Kumar Singh commented on ZOOKEEPER-2467: --- Thanks Joshi for this issue, as i had offline discussion with you i am taking this issue forward for complete. > NullPointerException when redo Command is passed negative value > --- > > Key: ZOOKEEPER-2467 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2467 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.4.8, 3.5.2 > Environment: Linux , windows >Reporter: Joshi Shankar >Assignee: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.4.10, 3.5.3 > > Attachments: ZOOKEEPER-2467-1.patch, ZOOKEEPER-2467-final.patch, > ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch > > > When negative value of argument is passed to redo command . > [zk: localhost:2181(CONNECTED) 0] redo -1 > Exception in thread "main" java.lang.NullPointerException > at java.util.StringTokenizer.(Unknown Source) > at java.util.StringTokenizer.(Unknown Source) > at > org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.parseCommand(ZooKeeperMain.java:227) > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:645) > at > org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:588) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:323) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:282) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2587) Not handled negative scenario for redo command
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15551654#comment-15551654 ] Rakesh Kumar Singh commented on ZOOKEEPER-2587: --- Thanks Rakesh R . > Not handled negative scenario for redo command > -- > > Key: ZOOKEEPER-2587 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2587 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.5.1, 3.5.2 > > Attachments: ZOOKEEPER-2587.patch, ZOOKEEPER-2587.patch > > > [zk: localhost:2181(CONNECTED) 2] redo -1 > Exception in thread "main" java.lang.NullPointerException > at java.util.StringTokenizer.(StringTokenizer.java:199) > at java.util.StringTokenizer.(StringTokenizer.java:221) > at > org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.parseCommand(ZooKeeperMain.java:219) > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:638) > at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:577) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:320) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:280) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2467) NullPointerException when redo Command is passed negative value
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2467: -- Attachment: ZOOKEEPER-2467.patch Pls review > NullPointerException when redo Command is passed negative value > --- > > Key: ZOOKEEPER-2467 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2467 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.4.8, 3.5.2 > Environment: Linux , windows >Reporter: Joshi Shankar >Assignee: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.4.10, 3.5.3 > > Attachments: ZOOKEEPER-2467-1.patch, ZOOKEEPER-2467-final.patch, > ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch > > > When negative value of argument is passed to redo command . > [zk: localhost:2181(CONNECTED) 0] redo -1 > Exception in thread "main" java.lang.NullPointerException > at java.util.StringTokenizer.(Unknown Source) > at java.util.StringTokenizer.(Unknown Source) > at > org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.parseCommand(ZooKeeperMain.java:227) > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:645) > at > org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:588) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:323) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:282) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ZOOKEEPER-2467) NullPointerException when redo Command is passed negative value
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh reassigned ZOOKEEPER-2467: - Assignee: Rakesh Kumar Singh (was: Joshi Shankar) > NullPointerException when redo Command is passed negative value > --- > > Key: ZOOKEEPER-2467 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2467 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.4.8, 3.5.2 > Environment: Linux , windows >Reporter: Joshi Shankar >Assignee: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.4.10, 3.5.3 > > Attachments: ZOOKEEPER-2467-1.patch, ZOOKEEPER-2467-final.patch, > ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch, ZOOKEEPER-2467.patch > > > When negative value of argument is passed to redo command . > [zk: localhost:2181(CONNECTED) 0] redo -1 > Exception in thread "main" java.lang.NullPointerException > at java.util.StringTokenizer.(Unknown Source) > at java.util.StringTokenizer.(Unknown Source) > at > org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.parseCommand(ZooKeeperMain.java:227) > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:645) > at > org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:588) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:323) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:282) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2587) Not handled negative scenario for redo command
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2587: -- Attachment: ZOOKEEPER-2587.patch Added fix and testcase > Not handled negative scenario for redo command > -- > > Key: ZOOKEEPER-2587 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2587 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.5.1, 3.5.2 > > Attachments: ZOOKEEPER-2587.patch, ZOOKEEPER-2587.patch > > > [zk: localhost:2181(CONNECTED) 2] redo -1 > Exception in thread "main" java.lang.NullPointerException > at java.util.StringTokenizer.(StringTokenizer.java:199) > at java.util.StringTokenizer.(StringTokenizer.java:221) > at > org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.parseCommand(ZooKeeperMain.java:219) > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:638) > at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:577) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:320) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:280) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2556) peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2556: -- Attachment: ZOOKEEPER-2556.patch > peerType remains as "observer" in zoo.cfg even though we change the node from > observer to participant runtime > - > > Key: ZOOKEEPER-2556 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2556 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > Attachments: ZOOKEEPER-2556.patch > > > peerType remains as "observer" in zoo.cfg even though we change the node from > observer to participant runtime > Steps to reproduce:- > 1. Start zookeeper in cluster with one node as observer by configuring > peerType=observer in zoo.cfg and server.2=10.18.219.50:2888:3888:observer;2181 > 2. Start the cluster > 3. start a client and change the node from observer to participant, the > configuration related to peertype remained same though other things like > clientport got from zoo.cfg > >reconfig -remove 2 -add 2=10.18.219.50:2888:3888:participant;2181 > We should either remove this parameter or update with correct node type at > run time -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2556) peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528438#comment-15528438 ] Rakesh Kumar Singh commented on ZOOKEEPER-2556: --- Thank you [~shralex] :) > peerType remains as "observer" in zoo.cfg even though we change the node from > observer to participant runtime > - > > Key: ZOOKEEPER-2556 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2556 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > > peerType remains as "observer" in zoo.cfg even though we change the node from > observer to participant runtime > Steps to reproduce:- > 1. Start zookeeper in cluster with one node as observer by configuring > peerType=observer in zoo.cfg and server.2=10.18.219.50:2888:3888:observer;2181 > 2. Start the cluster > 3. start a client and change the node from observer to participant, the > configuration related to peertype remained same though other things like > clientport got from zoo.cfg > >reconfig -remove 2 -add 2=10.18.219.50:2888:3888:participant;2181 > We should either remove this parameter or update with correct node type at > run time -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2556) peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528384#comment-15528384 ] Rakesh Kumar Singh commented on ZOOKEEPER-2556: --- [~shralex] Do i need to add testcase for this change.? > peerType remains as "observer" in zoo.cfg even though we change the node from > observer to participant runtime > - > > Key: ZOOKEEPER-2556 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2556 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > > peerType remains as "observer" in zoo.cfg even though we change the node from > observer to participant runtime > Steps to reproduce:- > 1. Start zookeeper in cluster with one node as observer by configuring > peerType=observer in zoo.cfg and server.2=10.18.219.50:2888:3888:observer;2181 > 2. Start the cluster > 3. start a client and change the node from observer to participant, the > configuration related to peertype remained same though other things like > clientport got from zoo.cfg > >reconfig -remove 2 -add 2=10.18.219.50:2888:3888:participant;2181 > We should either remove this parameter or update with correct node type at > run time -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2587) Not handled negative scenario for redo command
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2587: -- Attachment: ZOOKEEPER-2587.patch Proving patch for this issue > Not handled negative scenario for redo command > -- > > Key: ZOOKEEPER-2587 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2587 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.5.1, 3.5.2 > > Attachments: ZOOKEEPER-2587.patch > > > [zk: localhost:2181(CONNECTED) 2] redo -1 > Exception in thread "main" java.lang.NullPointerException > at java.util.StringTokenizer.(StringTokenizer.java:199) > at java.util.StringTokenizer.(StringTokenizer.java:221) > at > org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.parseCommand(ZooKeeperMain.java:219) > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:638) > at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:577) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:320) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:280) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2532) zkCli throwing nullpointerException instead it should provide help when invalid input is entered
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2532: -- Attachment: ZOOKEEPER-2532.patch > zkCli throwing nullpointerException instead it should provide help when > invalid input is entered > > > Key: ZOOKEEPER-2532 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2532 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.5.3, 3.6.0 > > Attachments: ZOOKEEPER-2532.patch, ZOOKEEPER-2532.patch > > > 1. a) Connect to zookeeper using zkCli > b) just input space and then hit enter > 2. a) Connect to zookeeper using zkCli and hit enter it will come as > connected > b) just input space and then hit enter > Console log is as below:- > [zk: localhost:2181(CONNECTING) 0] 2016-08-25 16:54:48,143 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxnSocketNetty$ZKClientPipelineFactory@363] > - SSL handler added for channel: null > 2016-08-25 16:54:48,175 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxn$SendThread@980] - Socket > connection established, initiating session, client: /0:0:0:0:0:0:0:1:44592, > server: localhost/0:0:0:0:0:0:0:1:2181 > 2016-08-25 16:54:48,178 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxnSocketNetty$1@146] - channel is > connected: [id: 0xd03f4226, /0:0:0:0:0:0:0:1:44592 => > localhost/0:0:0:0:0:0:0:1:2181] > 2016-08-25 16:54:48,288 [myid:] - INFO [New I/O worker > #1:ClientCnxn$SendThread@1400] - Session establishment complete on server > localhost/0:0:0:0:0:0:0:1:2181, sessionid = 0x101a00305cc0005, negotiated > timeout = 3 > WATCHER:: > WatchedEvent state:SyncConnected type:None path:null > > Exception in thread "main" java.lang.NullPointerException > at > org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.getArgArray(ZooKeeperMain.java:171) > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:613) > at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:577) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:320) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:280) > > After connection is established, input space and hit enter > [zk: localhost:2181(CONNECTING) 0] 2016-08-25 16:56:22,445 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxnSocketNetty$ZKClientPipelineFactory@363] > - SSL handler added for channel: null > 2016-08-25 16:56:22,481 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxn$SendThread@980] - Socket > connection established, initiating session, client: /0:0:0:0:0:0:0:1:44594, > server: localhost/0:0:0:0:0:0:0:1:2181 > 2016-08-25 16:56:22,484 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxnSocketNetty$1@146] - channel is > connected: [id: 0xe6d3a461, /0:0:0:0:0:0:0:1:44594 => > localhost/0:0:0:0:0:0:0:1:2181] > 2016-08-25 16:56:22,597 [myid:] - INFO [New I/O worker > #1:ClientCnxn$SendThread@1400] - Session establishment complete on server > localhost/0:0:0:0:0:0:0:1:2181, sessionid = 0x101a00305cc0007, negotiated > timeout = 3 > WATCHER:: > WatchedEvent state:SyncConnected type:None path:null > [zk: localhost:2181(CONNECTED) 0] > Exception in thread "main" java.lang.NullPointerException > at > org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.getArgArray(ZooKeeperMain.java:171) > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:613) > at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:577) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:320) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:280) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2556) peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15515520#comment-15515520 ] Rakesh Kumar Singh commented on ZOOKEEPER-2556: --- [~shralex]Thanks for feedback. > peerType remains as "observer" in zoo.cfg even though we change the node from > observer to participant runtime > - > > Key: ZOOKEEPER-2556 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2556 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > > peerType remains as "observer" in zoo.cfg even though we change the node from > observer to participant runtime > Steps to reproduce:- > 1. Start zookeeper in cluster with one node as observer by configuring > peerType=observer in zoo.cfg and server.2=10.18.219.50:2888:3888:observer;2181 > 2. Start the cluster > 3. start a client and change the node from observer to participant, the > configuration related to peertype remained same though other things like > clientport got from zoo.cfg > >reconfig -remove 2 -add 2=10.18.219.50:2888:3888:participant;2181 > We should either remove this parameter or update with correct node type at > run time -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ZOOKEEPER-2533) Close the zkCli using "close" command and then connect using "connect" then provide some invalid input, it closing the channel and connecting again
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh reassigned ZOOKEEPER-2533: - Assignee: Rakesh Kumar Singh > Close the zkCli using "close" command and then connect using "connect" then > provide some invalid input, it closing the channel and connecting again > --- > > Key: ZOOKEEPER-2533 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2533 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > > Close the zkCli using "close" command and then connect using "connect" then > provide some invalid input, it closing the channel and connecting again > Steps to reproduce:- > 1. Connect the Zookeeper server using zkCli > 2. close the connection using "close" > 3. Connect again using "connect host" > 4. Once connected, input space " " and hit enter > It is closing the channel and establishing again. > Console log is as below:- > [zk: localhost:2181(CONNECTED) 5] close > 2016-08-25 16:59:04,854 [myid:] - INFO [main:ClientCnxnSocketNetty@201] - > channel is told closing > 2016-08-25 16:59:04,855 [myid:] - INFO [main:ZooKeeper@1110] - Session: > 0x101a00305cc0008 closed > [zk: localhost:2181(CLOSED) 6] 2016-08-25 16:59:04,855 [myid:] - INFO > [main-EventThread:ClientCnxn$EventThread@542] - EventThread shut down for > session: 0x101a00305cc0008 > 2016-08-25 16:59:04,856 [myid:] - INFO [New I/O worker > #1:ClientCnxnSocketNetty$ZKClientHandler@377] - channel is disconnected: [id: > 0xd9735868, /0:0:0:0:0:0:0:1:44595 :> localhost/0:0:0:0:0:0:0:1:2181] > 2016-08-25 16:59:04,856 [myid:] - INFO [New I/O worker > #1:ClientCnxnSocketNetty@201] - channel is told closing > connect 10.18.101.80 > 2016-08-25 16:59:14,410 [myid:] - INFO [main:ZooKeeper@716] - Initiating > client connection, connectString=10.18.101.80 sessionTimeout=3 > watcher=org.apache.zookeeper.ZooKeeperMain$MyWatcher@19c50523 > [zk: 10.18.101.80(CONNECTING) 7] 2016-08-25 16:59:14,417 [myid:] - INFO > [main-SendThread(10.18.101.80:2181):ClientCnxn$SendThread@1138] - Opening > socket connection to server 10.18.101.80/10.18.101.80:2181. Will not attempt > to authenticate using SASL (unknown error) > 2016-08-25 16:59:14,426 [myid:] - INFO > [main-SendThread(10.18.101.80:2181):ClientCnxnSocketNetty$ZKClientPipelineFactory@363] > - SSL handler added for channel: null > 2016-08-25 16:59:14,428 [myid:] - INFO [New I/O worker > #10:ClientCnxn$SendThread@980] - Socket connection established, initiating > session, client: /10.18.101.80:58871, server: 10.18.101.80/10.18.101.80:2181 > 2016-08-25 16:59:14,428 [myid:] - INFO [New I/O worker > #10:ClientCnxnSocketNetty$1@146] - channel is connected: [id: 0xa8f6b724, > /10.18.101.80:58871 => 10.18.101.80/10.18.101.80:2181] > 2016-08-25 16:59:14,473 [myid:] - INFO [New I/O worker > #10:ClientCnxn$SendThread@1400] - Session establishment complete on server > 10.18.101.80/10.18.101.80:2181, sessionid = 0x101a00305cc0009, negotiated > timeout = 3 > WATCHER:: > WatchedEvent state:SyncConnected type:None path:null -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ZOOKEEPER-2545) Keep maintaining the old zoo.cfg.dynamic* files which will keep eating system memory which is getting generated as part of reconfig execution
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh reassigned ZOOKEEPER-2545: - Assignee: Rakesh Kumar Singh > Keep maintaining the old zoo.cfg.dynamic* files which will keep eating system > memory which is getting generated as part of reconfig execution > - > > Key: ZOOKEEPER-2545 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2545 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh > > Keep maintaining the old zoo.cfg.dynamic* files which will be getting created > every time when "reconfig" is executed > Steps to reproduce:-1 > 1. Setup the zookeeper in cluster mode and start > 2. trying running reconfig command like > >reconfig -remove 3 -add 1=10.18.101.80:2888:3888;2181 > 3. It will create new zoo.cfg.dynamic in conf folder > The problem is it is not deleting the old zoo.cfg.dynamic* files which will > keep eating the memory -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ZOOKEEPER-2540) When start zookeeper server by configuring the server details in dynamic configuration with passing the client port, wrong log info is logged
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh reassigned ZOOKEEPER-2540: - Assignee: Rakesh Kumar Singh > When start zookeeper server by configuring the server details in dynamic > configuration with passing the client port, wrong log info is logged > - > > Key: ZOOKEEPER-2540 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2540 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > > When start zookeeper server by configuring the server details in dynamic > configuration with passing the client port, wrong log info is logged:- > Configure the server details as below which contains client port as well and > remove the client port from zoo.cfg (as it is duplicate) :- > server.1=10.18.101.80:2888:3888:participant;2181 > server.2=10.18.219.50:2888:3888:participant;2181 > server.3=10.18.221.194:2888:3888:participant;2181 > Start the cluster, we can see message as > 2016-08-30 17:00:33,984 [myid:] - INFO [main:QuorumPeerConfig@306] - > clientPort is not set > which is not correct -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ZOOKEEPER-2556) peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh reassigned ZOOKEEPER-2556: - Assignee: Rakesh Kumar Singh > peerType remains as "observer" in zoo.cfg even though we change the node from > observer to participant runtime > - > > Key: ZOOKEEPER-2556 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2556 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > > peerType remains as "observer" in zoo.cfg even though we change the node from > observer to participant runtime > Steps to reproduce:- > 1. Start zookeeper in cluster with one node as observer by configuring > peerType=observer in zoo.cfg and server.2=10.18.219.50:2888:3888:observer;2181 > 2. Start the cluster > 3. start a client and change the node from observer to participant, the > configuration related to peertype remained same though other things like > clientport got from zoo.cfg > >reconfig -remove 2 -add 2=10.18.219.50:2888:3888:participant;2181 > We should either remove this parameter or update with correct node type at > run time -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ZOOKEEPER-2564) No message is prompted when trying to delete quota with different quota option
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh reassigned ZOOKEEPER-2564: - Assignee: Rakesh Kumar Singh > No message is prompted when trying to delete quota with different quota option > -- > > Key: ZOOKEEPER-2564 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2564 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > > No message is prompted when trying to delete quota with different quota > option. > Steps to reproduce:- > 1. Start zookeeper in cluster mode > 2. Create some node and set quota like > setquota -n 10 /test > 3. Now try to delete as below:- > delquota -b /test > Here no message/exception is prompted. We should prompt message like > "Byte Quota does not exist for /test" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ZOOKEEPER-2563) delquota -[n|b] is not deleting the set quota properly
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh reassigned ZOOKEEPER-2563: - Assignee: Rakesh Kumar Singh > delquota -[n|b] is not deleting the set quota properly > -- > > Key: ZOOKEEPER-2563 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2563 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh > > delquota -[n|b] is not deleting the set quota properly > Steps to reproduce:- > 1. Start zookeeper in cluster mode (ssl) > 2. create some node say /test > 3. Run command as listquota says (as expected) > quota for /test does not exist > 4. setquota let say > setquota -n 10 /test > 5. Now try to delete this as below > delquota -n /test > 6. now check the quota > [zk: localhost:2181(CONNECTED) 1] listquota /test > absolute path is /zookeeper/quota/test/zookeeper_limits > Output quota for /test count=-1,bytes=-1 > Output stat for /test count=1,bytes=5 > 7. Here it is not deleted quota node for test > 8. Now try to set some new quota > It fails as it is not deleted correctly while delete > [zk: localhost:2181(CONNECTED) 3] setquota -n 11 /test > Command failed: java.lang.IllegalArgumentException: /test has a parent > /zookeeper/quota/test which has a quota > But through delquota it is able to delete -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ZOOKEEPER-2559) Failed to delete the set quota for ephemeral node when the node is deleted because of client session closed
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh reassigned ZOOKEEPER-2559: - Assignee: Rakesh Kumar Singh > Failed to delete the set quota for ephemeral node when the node is deleted > because of client session closed > --- > > Key: ZOOKEEPER-2559 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2559 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh > > Failed to delete the set quota for ephemeral node when the node is deleted > because of client session closed > [zk: localhost:2181(CONNECTED) 0] create -e /e_test hello > Created /e_test > [zk: localhost:2181(CONNECTED) 1] setquota -n 10 /e_test > [zk: localhost:2181(CONNECTED) 2] listquota /e_test > absolute path is /zookeeper/quota/e_test/zookeeper_limits > Output quota for /e_test count=10,bytes=-1 > Output stat for /e_test count=1,bytes=5 > Now close the client connection and so the ephemeral node gets deleted. But > the corresponding quota is not getting deleted as below:- > [zk: localhost:2181(CONNECTED) 0] ls / > [test, test1, test3, zookeeper] > [zk: localhost:2181(CONNECTED) 1] listquota /e_test > absolute path is /zookeeper/quota/e_test/zookeeper_limits > Output quota for /e_test count=10,bytes=-1 > Output stat for /e_test count=0,bytes=0 > [zk: localhost:2181(CONNECTED) 2] > and so now again create the ephemeral node with same node and try to set the > quota, it will fail. > [zk: localhost:2181(CONNECTED) 2] create -e /e_test hello > Created /e_test > [zk: localhost:2181(CONNECTED) 3] setquota -n 10 /e_test > Command failed: java.lang.IllegalArgumentException: /e_test has a parent > /zookeeper/quota/e_test which has a quota > [zk: localhost:2181(CONNECTED) 4] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ZOOKEEPER-2565) listquota should display the quota even it is set on parent/child node
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh reassigned ZOOKEEPER-2565: - Assignee: Rakesh Kumar Singh > listquota should display the quota even it is set on parent/child node > - > > Key: ZOOKEEPER-2565 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2565 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > > listquota should display the quota even it is set on parent/child > node. As of now if we have a parent-child hierarchy for example n1->n2->n3 > and quota is set for n2. If we try to get quota details on n1 and n3 using > listquota, it says no quota set but if try to set the quota on those nodes it > fails saying quota is already set on parent node... > So listquota should fetch the quota set on any node in hierarchy with exact > path (on which quota is set) even though this api is called on any other node > in that hierarchy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ZOOKEEPER-2567) Error message is not correct when wrong argument is passed for "reconfig" cmd
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh reassigned ZOOKEEPER-2567: - Assignee: Rakesh Kumar Singh > Error message is not correct when wrong argument is passed for "reconfig" cmd > - > > Key: ZOOKEEPER-2567 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2567 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > > Error message is not correct when wrong argument is passed for "reconfig" cmd > Steps to reproduce:- > 1. Start zookeeper in cluster mode > 2. use reconfig cmd with wrong argument (pass : instead of ;) > [zk: localhost:2181(CONNECTED) 10] reconfig -remove 3 -add > 3=10.18.221.194:2888:3888:2181 > KeeperErrorCode = BadArguments for > Here error message is not complete and informative on client console. > The log is as below:- > 2016-09-08 18:54:08,701 [myid:1] - INFO [ProcessThread(sid:1 > cport:-1)::PrepRequestProcessor@512] - Incremental reconfig > 2016-09-08 18:54:08,702 [myid:1] - INFO [ProcessThread(sid:1 > cport:-1)::PrepRequestProcessor@843] - Got user-level KeeperException when > processing sessionid:0x100299b7eac type:reconfig cxid:0x7 > zxid:0x40004 txntype:-1 reqpath:n/a Error Path:Reconfiguration failed > Error:KeeperErrorCode = BadArguments for Reconfiguration failed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ZOOKEEPER-2580) ErrorMessage is not correct when set IP acl and try to set again from another machine
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh reassigned ZOOKEEPER-2580: - Assignee: Rakesh Kumar Singh > ErrorMessage is not correct when set IP acl and try to set again from another > machine > - > > Key: ZOOKEEPER-2580 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2580 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > > set IP acl and try to set again from another machine:- > [zk: localhost:2181(CONNECTED) 11] setAcl /ip_test ip:10.18.101.80:crdwa > KeeperErrorCode = NoAuth for /ip_test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ZOOKEEPER-2569) plain password is stored when set individual ACL using digest scheme
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh reassigned ZOOKEEPER-2569: - Assignee: Rakesh Kumar Singh > plain password is stored when set individual ACL using digest scheme > > > Key: ZOOKEEPER-2569 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2569 > Project: ZooKeeper > Issue Type: Bug > Components: security >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh > > Plain password is stored when set individual ACL using digest scheme instead > of storing the username and encoded hash string of > [zk: localhost:2181(CONNECTED) 13] addauth digest user:pass > [zk: localhost:2181(CONNECTED) 14] setAcl /newNode digest:user:pass:crdwa > [zk: localhost:2181(CONNECTED) 15] getAcl /newNode > 'digest,'user:pass > : cdrwa > [zk: localhost:2181(CONNECTED) 16] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ZOOKEEPER-2583) Using one client able to access the znode with localhost but fails from another client when IP ACL is set for znode using 127.0.0.1
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh reassigned ZOOKEEPER-2583: - Assignee: Rakesh Kumar Singh > Using one client able to access the znode with localhost but fails from > another client when IP ACL is set for znode using 127.0.0.1 > --- > > Key: ZOOKEEPER-2583 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2583 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > > Using one client able to access the znode with localhost but fails from > another client when IP ACL is set for znode using 127.0.0.1 > Start zookeeper in cluster mode. > Client 1 :- > [zk: localhost:2181(CONNECTED) 11] create /ip_test hello > Created /ip_test > [zk: localhost:2181(CONNECTED) 12] setAcl /ip_test > ip_testip_test4 > [zk: localhost:2181(CONNECTED) 12] setAcl /ip_test ip:127.0.0.1:crdwa > [zk: localhost:2181(CONNECTED) 13] get /ip_test > hello > [zk: localhost:2181(CONNECTED) 14] set /ip_test hi > [zk: localhost:2181(CONNECTED) 15] > Client 2 :- > [zk: localhost:2181(CONNECTED) 0] get /ip_test > Authentication is not valid : /ip_test > [zk: localhost:2181(CONNECTED) 1] getAcl /ip_test > 'ip,'127.0.0.1 > : cdrwa > [zk: localhost:2181(CONNECTED) 2] quit > now quit the client connection and connect again using 127.0.0.1 (like :- > ./zkCli.sh -server 127.0.0.1:2181) > [zk: 127.0.0.1:2181(CONNECTED) 0] get /ip_test > hi -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ZOOKEEPER-2584) when setquota for a znode and set ip/user ACL on /zookeeper/quota, still able to delete the quota from client with another ip though it says "Authentication is not v
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh reassigned ZOOKEEPER-2584: - Assignee: Rakesh Kumar Singh > when setquota for a znode and set ip/user ACL on /zookeeper/quota, still able > to delete the quota from client with another ip though it says > "Authentication is not valid" > -- > > Key: ZOOKEEPER-2584 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2584 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh > > when setquota for a znode and set ip/user ACL on /zookeeper/quota, still able > to delete the quota from client with another ip though it says > "Authentication is not valid" > >> Set quota and ip ACL from one client (with IP 10.18.101.80) > [zk: 10.18.101.80:2181(CONNECTED) 9] setquota -n 10 /test > [zk: 10.18.101.80:2181(CONNECTED) 10] setAcl /zookeeper/quota > ip:10.18.101.80:crdwa > [zk: 10.18.101.80:2181(CONNECTED) 11] > >> Try to delete the set quota using different client(with ip 10.18.219.50) > [zk: 10.18.219.50:2181(CONNECTED) 22] listquota /test > absolute path is /zookeeper/quota/test/zookeeper_limits > Output quota for /test count=10,bytes=-1 > Output stat for /test count=1,bytes=5 > [zk: 10.18.219.50:2181(CONNECTED) 23] delquota /test > Authentication is not valid : /zookeeper/quota/test > [zk: 10.18.219.50:2181(CONNECTED) 24] listquota /test > absolute path is /zookeeper/quota/test/zookeeper_limits > quota for /test does not exist. > >> Here quota has been deleted though it is saying "Authentication is not > >> valid.." which is not correct. > Now try to set the quota from another ip itself, it fails which is as expected > [zk: 10.18.219.50:2181(CONNECTED) 25] setquota -n 10 /test > Authentication is not valid : /zookeeper/quota/test > [zk: 10.18.219.50:2181(CONNECTED) 26] listquota /test > absolute path is /zookeeper/quota/test/zookeeper_limits > quota for /test does not exist. > >> Sameway when we set user ACL... > [zk: 10.18.101.80:2181(CONNECTED) 26] addauth digest user:pass > [zk: 10.18.101.80:2181(CONNECTED) 27] create /test hello > Node already exists: /test > [zk: 10.18.101.80:2181(CONNECTED) 28] delete /test > [zk: 10.18.101.80:2181(CONNECTED) 29] create /test hello > Created /test > [zk: 10.18.101.80:2181(CONNECTED) 30] > [zk: 10.18.101.80:2181(CONNECTED) 30] setquota -n 10 /test > [zk: 10.18.101.80:2181(CONNECTED) 31] setAcl /zookeeper/quota > auth:user:pass:crdwa > [zk: 10.18.101.80:2181(CONNECTED) 32] > [zk: 10.18.219.50:2181(CONNECTED) 27] listquota /test > absolute path is /zookeeper/quota/test/zookeeper_limits > Output quota for /test count=10,bytes=-1 > Output stat for /test count=1,bytes=5 > [zk: 10.18.219.50:2181(CONNECTED) 28] delquota /test > Authentication is not valid : /zookeeper/quota/test > [zk: 10.18.219.50:2181(CONNECTED) 29] listquota /test > absolute path is /zookeeper/quota/test/zookeeper_limits > quota for /test does not exist. > [zk: 10.18.219.50:2181(CONNECTED) 30] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2599) Quorum with 3 nodes, stop 2 nodes and let one running, install and configure new quorum where one node details is common but now has configuration of new quorum. comm
Rakesh Kumar Singh created ZOOKEEPER-2599: - Summary: Quorum with 3 nodes, stop 2 nodes and let one running, install and configure new quorum where one node details is common but now has configuration of new quorum. common node getting synced the configuration with previous quorum Key: ZOOKEEPER-2599 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2599 Project: ZooKeeper Issue Type: Bug Affects Versions: 3.5.1 Reporter: Rakesh Kumar Singh Priority: Critical Start an quorum with 3 (let say A, B, C) zookeepers, stop 2 zookeepers and let one running, install and configure new quorum (A, A2, A3, A4, A5) where A is common but now has configuration of new quorum. When start A, it getting synced the configuration with previous quorum Steps to reproduce:- 1. Configure and start quorum of 3 nodes (A, B, C) -> 1st quorum 2. stop 2 nodes and let running 3rd node (say C) 3. Create new quorum of 5 nodes (A, A2, A3, A4, A5) where A has same IP and port which was used in 1st quorum but A's configuration is as per new quorum (where details of A, A2, A3, A4, A5) are present and not B & C. 4. Now start 2nd quorum. Here A's dynamic configuration is getting changed according to 1st quorum Problems:- 1. Now A node is neither syncing all data with 1st quorum nor with 2nd quorum 2. Big security flaw and the whole quorum can be screwed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2580) ErrorMessage is not correct when set IP acl and try to set again from another machine
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15512695#comment-15512695 ] Rakesh Kumar Singh commented on ZOOKEEPER-2580: --- [~arshad.mohammad] thanks..but i think you need to improve your english to understand the problem which will help to understand the problem at 1st level itself. Read this issue again. > ErrorMessage is not correct when set IP acl and try to set again from another > machine > - > > Key: ZOOKEEPER-2580 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2580 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Priority: Minor > > set IP acl and try to set again from another machine:- > [zk: localhost:2181(CONNECTED) 11] setAcl /ip_test ip:10.18.101.80:crdwa > KeeperErrorCode = NoAuth for /ip_test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2569) plain password is stored when set individual ACL using digest scheme
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15508854#comment-15508854 ] Rakesh Kumar Singh commented on ZOOKEEPER-2569: --- This should be problem only..hope we can discuss before making conclusion. > plain password is stored when set individual ACL using digest scheme > > > Key: ZOOKEEPER-2569 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2569 > Project: ZooKeeper > Issue Type: Bug > Components: security >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh > > Plain password is stored when set individual ACL using digest scheme instead > of storing the username and encoded hash string of > [zk: localhost:2181(CONNECTED) 13] addauth digest user:pass > [zk: localhost:2181(CONNECTED) 14] setAcl /newNode digest:user:pass:crdwa > [zk: localhost:2181(CONNECTED) 15] getAcl /newNode > 'digest,'user:pass > : cdrwa > [zk: localhost:2181(CONNECTED) 16] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2569) plain password is stored when set individual ACL using digest scheme
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15508851#comment-15508851 ] Rakesh Kumar Singh commented on ZOOKEEPER-2569: --- @Arshad Mohammad : Don't you think if the passed arguments are wrong so system should not accept. > plain password is stored when set individual ACL using digest scheme > > > Key: ZOOKEEPER-2569 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2569 > Project: ZooKeeper > Issue Type: Bug > Components: security >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh > > Plain password is stored when set individual ACL using digest scheme instead > of storing the username and encoded hash string of > [zk: localhost:2181(CONNECTED) 13] addauth digest user:pass > [zk: localhost:2181(CONNECTED) 14] setAcl /newNode digest:user:pass:crdwa > [zk: localhost:2181(CONNECTED) 15] getAcl /newNode > 'digest,'user:pass > : cdrwa > [zk: localhost:2181(CONNECTED) 16] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2585) ACL with SSL is not working
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15508831#comment-15508831 ] Rakesh Kumar Singh commented on ZOOKEEPER-2585: --- [~arshad.mohammad] As i mentioned earlier also, pls try to understand the problem before making conclusion. If any clarity required can be discussed or can be followed the steps mentioned in the issue to understand the problem. In this issue pls try to perform the steps mentioned here in 2 case- one when zookeeper started in ssl mode and another when zookeeper started in non-ssl mode and will get the difference. > ACL with SSL is not working > --- > > Key: ZOOKEEPER-2585 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2585 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Priority: Critical > > Set ACL with SSL is not working > Steps to reproduce:- > 1. Start zookeeper in ssl mode in standalone > 2. Connect zookeeper from zookeeper client (using zkCli.sh) > 3. add auth and set ACL as below and then quit the client :- > [zk: localhost:2181(CONNECTED) 0] addauth digest u1:p1 > [zk: localhost:2181(CONNECTED) 1] create /test_auth hello > Created /test_auth > [zk: localhost:2181(CONNECTED) 2] setAcl /test_auth auth:u1:p1:crdwa > [zk: localhost:2181(CONNECTED) 3] get /test_auth > hello > [zk: localhost:2181(CONNECTED) 4] quit > 4. Connect again zookeeper from zookeeper client (using zkCli.sh) > 5. Try to access the znode, try to set the data and so on, everything is > allowed > [zk: localhost:2181(CONNECTED) 2] set /test_auth hello1 > [zk: localhost:2181(CONNECTED) 3] get /test_auth > hello1 > [zk: localhost:2181(CONNECTED) 1] getAcl /test_auth > 'x509,'CN=locahost%2COU=CS%2CO=HUAWEI%2CL=Shenzhen%2CST=Guangdong%2CC=CHINA > : cdrwa > 'digest,'u1:fpT/y03U+EjItKZOSLGvjnJlyng= > : cdrwa -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (ZOOKEEPER-2589) Not able to access znode if IP ACL is set on a znode when zookeeper started in ssl mode
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15508781#comment-15508781 ] Rakesh Kumar Singh edited comment on ZOOKEEPER-2589 at 9/21/16 5:12 AM: Thanks for feedback. will verify against that patch and feedback was (Author: rakeshsingh): Thanks for feedback will verify against that patch and feedback > Not able to access znode if IP ACL is set on a znode when zookeeper started > in ssl mode > > > Key: ZOOKEEPER-2589 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2589 > Project: ZooKeeper > Issue Type: Bug >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh > > Not able to access znode if IP ACL is set on a znode when zookeeper started > in ssl mode. > Steps to reproduce:- > 1. Start zookeeper in SSL (standalone) mode > 2. Create a znode > 3. set ip ACL and connect the zkCli and try to access, it does not allow. > [zk: localhost:2181(CONNECTED) 3] setAcl /test ip:127.0.0.1:crdwa > [zk: localhost:2181(CONNECTED) 5] quit > >> start the zkCli with 127.0.0.1 and trying access the znode > [zk: 127.0.0.1:2181(CONNECTED) 0] get -s /test > Authentication is not valid : /test > [zk: 127.0.0.1:2181(CONNECTED) 1] getAcl /test > 'ip,'127.0.0.1 > : cdrwa > [zk: 127.0.0.1:2181(CONNECTED) 2] get /test > Authentication is not valid : /test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2589) Not able to access znode if IP ACL is set on a znode when zookeeper started in ssl mode
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15508781#comment-15508781 ] Rakesh Kumar Singh commented on ZOOKEEPER-2589: --- Thanks for feedback will verify against that patch and feedback > Not able to access znode if IP ACL is set on a znode when zookeeper started > in ssl mode > > > Key: ZOOKEEPER-2589 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2589 > Project: ZooKeeper > Issue Type: Bug >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh > > Not able to access znode if IP ACL is set on a znode when zookeeper started > in ssl mode. > Steps to reproduce:- > 1. Start zookeeper in SSL (standalone) mode > 2. Create a znode > 3. set ip ACL and connect the zkCli and try to access, it does not allow. > [zk: localhost:2181(CONNECTED) 3] setAcl /test ip:127.0.0.1:crdwa > [zk: localhost:2181(CONNECTED) 5] quit > >> start the zkCli with 127.0.0.1 and trying access the znode > [zk: 127.0.0.1:2181(CONNECTED) 0] get -s /test > Authentication is not valid : /test > [zk: 127.0.0.1:2181(CONNECTED) 1] getAcl /test > 'ip,'127.0.0.1 > : cdrwa > [zk: 127.0.0.1:2181(CONNECTED) 2] get /test > Authentication is not valid : /test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2580) ErrorMessage is not correct when set IP acl and try to set again from another machine
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15508773#comment-15508773 ] Rakesh Kumar Singh commented on ZOOKEEPER-2580: --- [~arshad.mohammad] i think you are not trying to understand the problem before making your conclusion or comment. And any comment should not be just shake of comment. Here the problem is with error message and that to the user we can't give the error code as error message. > ErrorMessage is not correct when set IP acl and try to set again from another > machine > - > > Key: ZOOKEEPER-2580 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2580 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Priority: Minor > > set IP acl and try to set again from another machine:- > [zk: localhost:2181(CONNECTED) 11] setAcl /ip_test ip:10.18.101.80:crdwa > KeeperErrorCode = NoAuth for /ip_test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2521) space should be truncated while reading password for keystore/truststore which is required to configure while SSL enabled
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15508652#comment-15508652 ] Rakesh Kumar Singh commented on ZOOKEEPER-2521: --- Agree with Edward Ribeiro > space should be truncated while reading password for keystore/truststore > which is required to configure while SSL enabled > - > > Key: ZOOKEEPER-2521 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2521 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.5.3, 3.6.0 > > Attachments: ZOOKEEPER-2521.2.patch, ZOOKEEPER-2521.patch > > > space should be truncated while reading password for keystore/truststore > which is required to configure while SSL enabled. > As of now if we configure the password with any heading/trailing space, the > zookeeper server will fail to start. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2521) space should be truncated while reading password for keystore/truststore which is required to configure while SSL enabled
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15506077#comment-15506077 ] Rakesh Kumar Singh commented on ZOOKEEPER-2521: --- This is related to SSL configuration and we have SSL support from 3.5 onwards. > space should be truncated while reading password for keystore/truststore > which is required to configure while SSL enabled > - > > Key: ZOOKEEPER-2521 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2521 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Assignee: Edward Ribeiro >Priority: Minor > Fix For: 3.5.3, 3.6.0 > > Attachments: ZOOKEEPER-2521.patch > > > space should be truncated while reading password for keystore/truststore > which is required to configure while SSL enabled. > As of now if we configure the password with any heading/trailing space, the > zookeeper server will fail to start. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2521) space should be truncated while reading password for keystore/truststore which is required to configure while SSL enabled
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15505695#comment-15505695 ] Rakesh Kumar Singh commented on ZOOKEEPER-2521: --- Leading and trailing spaces could be trouble for people who are loose with copy and paste and ll be little difficult to figure out why authentication is failing. Otherwise ok with documenting. > space should be truncated while reading password for keystore/truststore > which is required to configure while SSL enabled > - > > Key: ZOOKEEPER-2521 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2521 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Assignee: Edward Ribeiro >Priority: Minor > Attachments: ZOOKEEPER-2521.patch > > > space should be truncated while reading password for keystore/truststore > which is required to configure while SSL enabled. > As of now if we configure the password with any heading/trailing space, the > zookeeper server will fail to start. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2592) Zookeeper is not recoverable once running system( machine on which zookeeper is running) is out of space
Rakesh Kumar Singh created ZOOKEEPER-2592: - Summary: Zookeeper is not recoverable once running system( machine on which zookeeper is running) is out of space Key: ZOOKEEPER-2592 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2592 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.2, 3.5.1 Reporter: Rakesh Kumar Singh Priority: Critical Zookeeper is not recoverable once running system( machine on which zookeeper is running) is out of space Steps to reproduce:- 1. Install zookeeper on standalone mode and start zookeeper 2. Make the machine physical memory full 3. Connect through client to zookeeper and trying create some znodes with some data. 4. After sometime creating further znode will not happened as complete memory is occupied 5. Now start creating space in that machine 6. Again connect through a client. Connection is fine. Now try to execute any command like "ls / " it fails even though now space is more than 11gb Client log:- BLR107042:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin # df -h Filesystem Size Used Avail Use% Mounted on /dev/xvda2 36G 24G 11G 70% / udev1.9G 116K 1.9G 1% /dev tmpfs 1.9G 0 1.9G 0% /dev/shm BLR107042:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin # ./zkCli.sh Connecting to localhost:2181 2016-09-19 22:50:20,227 [myid:] - INFO [main:Environment@109] - Client environment:zookeeper.version=3.5.1-alpha--1, built on 08/18/2016 08:20 GMT 2016-09-19 22:50:20,231 [myid:] - INFO [main:Environment@109] - Client environment:host.name=BLR107042 2016-09-19 22:50:20,231 [myid:] - INFO [main:Environment@109] - Client environment:java.version=1.7.0_79 2016-09-19 22:50:20,234 [myid:] - INFO [main:Environment@109] - Client environment:java.vendor=Oracle Corporation 2016-09-19 22:50:20,234 [myid:] - INFO [main:Environment@109] - Client environment:java.home=/usr/java/jdk1.7.0_79/jre 2016-09-19 22:50:20,234 [myid:] - INFO [main:Environment@109] - Client environment:java.class.path=/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../build/classes:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../build/lib/*.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/slf4j-log4j12-1.7.5.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/slf4j-api-1.7.5.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/servlet-api-2.5-20081211.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/netty-3.7.0.Final.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/log4j-1.2.16.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jline-2.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jetty-util-6.1.26.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jetty-6.1.26.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/javacc.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jackson-mapper-asl-1.9.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jackson-core-asl-1.9.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/commons-cli-1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/ant-eclipse-1.0-jvm1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../zookeeper-3.5.1-alpha.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../src/java/lib/ant-eclipse-1.0-jvm1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../conf:/usr/java/jdk1.7.0_79/lib 2016-09-19 22:50:20,234 [myid:] - INFO [main:Environment@109] - Client environment:java.library.path=/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib 2016-09-19 22:50:20,234 [myid:] - INFO [main:Environment@109] - Client environment:java.io.tmpdir=/tmp 2016-09-19 22:50:20,234 [myid:] - INFO [main:Environment@109] - Client environment:java.compiler= 2016-09-19 22:50:20,235 [myid:] - INFO [main:Environment@109] - Client environment:os.name=Linux 2016-09-19 22:50:20,235 [myid:] - INFO [main:Environment@109] - Client environment:os.arch=amd64 2016-09-19 22:50:20,235 [myid:] - INFO [main:Environment@109] - Client environment:os.version=3.0.76-0.11-default 2016-09-19 22:50:20,235 [myid:] - INFO [main:Environment@109] - Client environment:user.name=root 2016-09-19 22:50:20,235 [myid:] - INFO [main:Environment@109] - Client environment:user.home=/root 2016-09-19 22:50:20,235 [myid:] - INFO [main:Environment@109] - Client environment:user.dir=/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin 2016-09-19 22:50:20,235 [myid:] - INFO
[jira] [Created] (ZOOKEEPER-2589) Not able to access znode if IP ACL is set on a znode when zookeeper started in ssl mode
Rakesh Kumar Singh created ZOOKEEPER-2589: - Summary: Not able to access znode if IP ACL is set on a znode when zookeeper started in ssl mode Key: ZOOKEEPER-2589 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2589 Project: ZooKeeper Issue Type: Bug Affects Versions: 3.5.1 Reporter: Rakesh Kumar Singh Not able to access znode if IP ACL is set on a znode when zookeeper started in ssl mode. Steps to reproduce:- 1. Start zookeeper in SSL (standalone) mode 2. Create a znode 3. set ip ACL and connect the zkCli and try to access, it does not allow. [zk: localhost:2181(CONNECTED) 3] setAcl /test ip:127.0.0.1:crdwa [zk: localhost:2181(CONNECTED) 5] quit >> start the zkCli with 127.0.0.1 and trying access the znode [zk: 127.0.0.1:2181(CONNECTED) 0] get -s /test Authentication is not valid : /test [zk: 127.0.0.1:2181(CONNECTED) 1] getAcl /test 'ip,'127.0.0.1 : cdrwa [zk: 127.0.0.1:2181(CONNECTED) 2] get /test Authentication is not valid : /test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2531) Configuration as "zookeeper.secure=true/false" can be introduced and reading and verifying all ssl related configuration (like secureport, keystore, truststore, corre
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2531: -- Priority: Major (was: Minor) > Configuration as "zookeeper.secure=true/false" can be introduced and reading > and verifying all ssl related configuration (like secureport, keystore, > truststore, corresponding password) should be done only when > "zookeeper.secure" flag is true > - > > Key: ZOOKEEPER-2531 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2531 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh > > Configuration as "zookeeper.secure=true/false" can be introduced and reading > and verifying all ssl related configuration (like secureport, keystore, > truststore, corresponding password) should be done only when > "zookeeper.secure" flag is true -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2587) Not handled negative scenario for redo command
Rakesh Kumar Singh created ZOOKEEPER-2587: - Summary: Not handled negative scenario for redo command Key: ZOOKEEPER-2587 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2587 Project: ZooKeeper Issue Type: Bug Components: java client Reporter: Rakesh Kumar Singh Assignee: Rakesh Kumar Singh Priority: Minor Fix For: 3.5.1 [zk: localhost:2181(CONNECTED) 2] redo -1 Exception in thread "main" java.lang.NullPointerException at java.util.StringTokenizer.(StringTokenizer.java:199) at java.util.StringTokenizer.(StringTokenizer.java:221) at org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.parseCommand(ZooKeeperMain.java:219) at org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:638) at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:577) at org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:320) at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:280) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2532) zkCli throwing nullpointerException instead it should provide help when invalid input is entered
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493321#comment-15493321 ] Rakesh Kumar Singh commented on ZOOKEEPER-2532: --- Still QA being not triggered.. > zkCli throwing nullpointerException instead it should provide help when > invalid input is entered > > > Key: ZOOKEEPER-2532 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2532 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.5.3, 3.6.0 > > Attachments: ZOOKEEPER-2532.patch > > > 1. a) Connect to zookeeper using zkCli > b) just input space and then hit enter > 2. a) Connect to zookeeper using zkCli and hit enter it will come as > connected > b) just input space and then hit enter > Console log is as below:- > [zk: localhost:2181(CONNECTING) 0] 2016-08-25 16:54:48,143 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxnSocketNetty$ZKClientPipelineFactory@363] > - SSL handler added for channel: null > 2016-08-25 16:54:48,175 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxn$SendThread@980] - Socket > connection established, initiating session, client: /0:0:0:0:0:0:0:1:44592, > server: localhost/0:0:0:0:0:0:0:1:2181 > 2016-08-25 16:54:48,178 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxnSocketNetty$1@146] - channel is > connected: [id: 0xd03f4226, /0:0:0:0:0:0:0:1:44592 => > localhost/0:0:0:0:0:0:0:1:2181] > 2016-08-25 16:54:48,288 [myid:] - INFO [New I/O worker > #1:ClientCnxn$SendThread@1400] - Session establishment complete on server > localhost/0:0:0:0:0:0:0:1:2181, sessionid = 0x101a00305cc0005, negotiated > timeout = 3 > WATCHER:: > WatchedEvent state:SyncConnected type:None path:null > > Exception in thread "main" java.lang.NullPointerException > at > org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.getArgArray(ZooKeeperMain.java:171) > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:613) > at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:577) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:320) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:280) > > After connection is established, input space and hit enter > [zk: localhost:2181(CONNECTING) 0] 2016-08-25 16:56:22,445 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxnSocketNetty$ZKClientPipelineFactory@363] > - SSL handler added for channel: null > 2016-08-25 16:56:22,481 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxn$SendThread@980] - Socket > connection established, initiating session, client: /0:0:0:0:0:0:0:1:44594, > server: localhost/0:0:0:0:0:0:0:1:2181 > 2016-08-25 16:56:22,484 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxnSocketNetty$1@146] - channel is > connected: [id: 0xe6d3a461, /0:0:0:0:0:0:0:1:44594 => > localhost/0:0:0:0:0:0:0:1:2181] > 2016-08-25 16:56:22,597 [myid:] - INFO [New I/O worker > #1:ClientCnxn$SendThread@1400] - Session establishment complete on server > localhost/0:0:0:0:0:0:0:1:2181, sessionid = 0x101a00305cc0007, negotiated > timeout = 3 > WATCHER:: > WatchedEvent state:SyncConnected type:None path:null > [zk: localhost:2181(CONNECTED) 0] > Exception in thread "main" java.lang.NullPointerException > at > org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.getArgArray(ZooKeeperMain.java:171) > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:613) > at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:577) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:320) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:280) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2585) ACL with SSL is not working
Rakesh Kumar Singh created ZOOKEEPER-2585: - Summary: ACL with SSL is not working Key: ZOOKEEPER-2585 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2585 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.1 Reporter: Rakesh Kumar Singh Priority: Critical Set ACL with SSL is not working Steps to reproduce:- 1. Start zookeeper in ssl mode in standalone 2. Connect zookeeper from zookeeper client (using zkCli.sh) 3. add auth and set ACL as below and then quit the client :- [zk: localhost:2181(CONNECTED) 0] addauth digest u1:p1 [zk: localhost:2181(CONNECTED) 1] create /test_auth hello Created /test_auth [zk: localhost:2181(CONNECTED) 2] setAcl /test_auth auth:u1:p1:crdwa [zk: localhost:2181(CONNECTED) 3] get /test_auth hello [zk: localhost:2181(CONNECTED) 4] quit 4. Connect again zookeeper from zookeeper client (using zkCli.sh) 5. Try to access the znode, try to set the data and so on, everything is allowed [zk: localhost:2181(CONNECTED) 2] set /test_auth hello1 [zk: localhost:2181(CONNECTED) 3] get /test_auth hello1 [zk: localhost:2181(CONNECTED) 1] getAcl /test_auth 'x509,'CN=locahost%2COU=CS%2CO=HUAWEI%2CL=Shenzhen%2CST=Guangdong%2CC=CHINA : cdrwa 'digest,'u1:fpT/y03U+EjItKZOSLGvjnJlyng= : cdrwa -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2584) when setquota for a znode and set ip/user ACL on /zookeeper/quota, still able to delete the quota from client with another ip though it says "Authentication is not va
Rakesh Kumar Singh created ZOOKEEPER-2584: - Summary: when setquota for a znode and set ip/user ACL on /zookeeper/quota, still able to delete the quota from client with another ip though it says "Authentication is not valid" Key: ZOOKEEPER-2584 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2584 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.1 Reporter: Rakesh Kumar Singh when setquota for a znode and set ip/user ACL on /zookeeper/quota, still able to delete the quota from client with another ip though it says "Authentication is not valid" >> Set quota and ip ACL from one client (with IP 10.18.101.80) [zk: 10.18.101.80:2181(CONNECTED) 9] setquota -n 10 /test [zk: 10.18.101.80:2181(CONNECTED) 10] setAcl /zookeeper/quota ip:10.18.101.80:crdwa [zk: 10.18.101.80:2181(CONNECTED) 11] >> Try to delete the set quota using different client(with ip 10.18.219.50) [zk: 10.18.219.50:2181(CONNECTED) 22] listquota /test absolute path is /zookeeper/quota/test/zookeeper_limits Output quota for /test count=10,bytes=-1 Output stat for /test count=1,bytes=5 [zk: 10.18.219.50:2181(CONNECTED) 23] delquota /test Authentication is not valid : /zookeeper/quota/test [zk: 10.18.219.50:2181(CONNECTED) 24] listquota /test absolute path is /zookeeper/quota/test/zookeeper_limits quota for /test does not exist. >> Here quota has been deleted though it is saying "Authentication is not >> valid.." which is not correct. Now try to set the quota from another ip itself, it fails which is as expected [zk: 10.18.219.50:2181(CONNECTED) 25] setquota -n 10 /test Authentication is not valid : /zookeeper/quota/test [zk: 10.18.219.50:2181(CONNECTED) 26] listquota /test absolute path is /zookeeper/quota/test/zookeeper_limits quota for /test does not exist. >> Sameway when we set user ACL... [zk: 10.18.101.80:2181(CONNECTED) 26] addauth digest user:pass [zk: 10.18.101.80:2181(CONNECTED) 27] create /test hello Node already exists: /test [zk: 10.18.101.80:2181(CONNECTED) 28] delete /test [zk: 10.18.101.80:2181(CONNECTED) 29] create /test hello Created /test [zk: 10.18.101.80:2181(CONNECTED) 30] [zk: 10.18.101.80:2181(CONNECTED) 30] setquota -n 10 /test [zk: 10.18.101.80:2181(CONNECTED) 31] setAcl /zookeeper/quota auth:user:pass:crdwa [zk: 10.18.101.80:2181(CONNECTED) 32] [zk: 10.18.219.50:2181(CONNECTED) 27] listquota /test absolute path is /zookeeper/quota/test/zookeeper_limits Output quota for /test count=10,bytes=-1 Output stat for /test count=1,bytes=5 [zk: 10.18.219.50:2181(CONNECTED) 28] delquota /test Authentication is not valid : /zookeeper/quota/test [zk: 10.18.219.50:2181(CONNECTED) 29] listquota /test absolute path is /zookeeper/quota/test/zookeeper_limits quota for /test does not exist. [zk: 10.18.219.50:2181(CONNECTED) 30] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ZOOKEEPER-2581) Not handled NullPointerException while creating key manager and trustManager
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh reassigned ZOOKEEPER-2581: - Assignee: Rakesh Kumar Singh > Not handled NullPointerException while creating key manager and trustManager > > > Key: ZOOKEEPER-2581 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2581 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh > > Not handled NullPointerException while creating key manager and trustManager:- > 2016-09-14 13:35:23,488 [myid:1] - ERROR > [CommitProcWorkThread-1:X509AuthenticationProvider@78] - Failed to create key > manager > org.apache.zookeeper.common.X509Exception$KeyManagerException: > java.lang.NullPointerException > at > org.apache.zookeeper.common.X509Util.createKeyManager(X509Util.java:129) > at > org.apache.zookeeper.server.auth.X509AuthenticationProvider.(X509AuthenticationProvider.java:75) > at > org.apache.zookeeper.server.auth.ProviderRegistry.initialize(ProviderRegistry.java:42) > at > org.apache.zookeeper.server.auth.ProviderRegistry.getProvider(ProviderRegistry.java:68) > at > org.apache.zookeeper.server.PrepRequestProcessor.checkACL(PrepRequestProcessor.java:319) > at > org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:324) > at > org.apache.zookeeper.server.quorum.CommitProcessor$CommitWorkRequest.doWork(CommitProcessor.java:296) > at > org.apache.zookeeper.server.WorkerService$ScheduledWorkRequest.run(WorkerService.java:162) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NullPointerException > at > org.apache.zookeeper.common.X509Util.createKeyManager(X509Util.java:113) > ... 10 more > 2016-09-14 13:35:23,489 [myid:1] - ERROR > [CommitProcWorkThread-1:X509AuthenticationProvider@90] - Failed to create > trust manager > org.apache.zookeeper.common.X509Exception$TrustManagerException: > java.lang.NullPointerException > at > org.apache.zookeeper.common.X509Util.createTrustManager(X509Util.java:158) > at > org.apache.zookeeper.server.auth.X509AuthenticationProvider.(X509AuthenticationProvider.java:87) > at > org.apache.zookeeper.server.auth.ProviderRegistry.initialize(ProviderRegistry.java:42) > at > org.apache.zookeeper.server.auth.ProviderRegistry.getProvider(ProviderRegistry.java:68) > at > org.apache.zookeeper.server.PrepRequestProcessor.checkACL(PrepRequestProcessor.java:319) > at > org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:324) > at > org.apache.zookeeper.server.quorum.CommitProcessor$CommitWorkRequest.doWork(CommitProcessor.java:296) > at > org.apache.zookeeper.server.WorkerService$ScheduledWorkRequest.run(WorkerService.java:162) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NullPointerException > at > org.apache.zookeeper.common.X509Util.createTrustManager(X509Util.java:143) > ... 10 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ZOOKEEPER-2581) Not handled NullPointerException while creating key manager and trustManager
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh reassigned ZOOKEEPER-2581: - Assignee: (was: Rakesh Kumar Singh) > Not handled NullPointerException while creating key manager and trustManager > > > Key: ZOOKEEPER-2581 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2581 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh > > Not handled NullPointerException while creating key manager and trustManager:- > 2016-09-14 13:35:23,488 [myid:1] - ERROR > [CommitProcWorkThread-1:X509AuthenticationProvider@78] - Failed to create key > manager > org.apache.zookeeper.common.X509Exception$KeyManagerException: > java.lang.NullPointerException > at > org.apache.zookeeper.common.X509Util.createKeyManager(X509Util.java:129) > at > org.apache.zookeeper.server.auth.X509AuthenticationProvider.(X509AuthenticationProvider.java:75) > at > org.apache.zookeeper.server.auth.ProviderRegistry.initialize(ProviderRegistry.java:42) > at > org.apache.zookeeper.server.auth.ProviderRegistry.getProvider(ProviderRegistry.java:68) > at > org.apache.zookeeper.server.PrepRequestProcessor.checkACL(PrepRequestProcessor.java:319) > at > org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:324) > at > org.apache.zookeeper.server.quorum.CommitProcessor$CommitWorkRequest.doWork(CommitProcessor.java:296) > at > org.apache.zookeeper.server.WorkerService$ScheduledWorkRequest.run(WorkerService.java:162) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NullPointerException > at > org.apache.zookeeper.common.X509Util.createKeyManager(X509Util.java:113) > ... 10 more > 2016-09-14 13:35:23,489 [myid:1] - ERROR > [CommitProcWorkThread-1:X509AuthenticationProvider@90] - Failed to create > trust manager > org.apache.zookeeper.common.X509Exception$TrustManagerException: > java.lang.NullPointerException > at > org.apache.zookeeper.common.X509Util.createTrustManager(X509Util.java:158) > at > org.apache.zookeeper.server.auth.X509AuthenticationProvider.(X509AuthenticationProvider.java:87) > at > org.apache.zookeeper.server.auth.ProviderRegistry.initialize(ProviderRegistry.java:42) > at > org.apache.zookeeper.server.auth.ProviderRegistry.getProvider(ProviderRegistry.java:68) > at > org.apache.zookeeper.server.PrepRequestProcessor.checkACL(PrepRequestProcessor.java:319) > at > org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:324) > at > org.apache.zookeeper.server.quorum.CommitProcessor$CommitWorkRequest.doWork(CommitProcessor.java:296) > at > org.apache.zookeeper.server.WorkerService$ScheduledWorkRequest.run(WorkerService.java:162) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NullPointerException > at > org.apache.zookeeper.common.X509Util.createTrustManager(X509Util.java:143) > ... 10 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2532) zkCli throwing nullpointerException instead it should provide help when invalid input is entered
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490977#comment-15490977 ] Rakesh Kumar Singh commented on ZOOKEEPER-2532: --- Pls review. Not sure why CI is not running on this submit. > zkCli throwing nullpointerException instead it should provide help when > invalid input is entered > > > Key: ZOOKEEPER-2532 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2532 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.5.1, 3.5.2 > > Attachments: ZOOKEEPER-2532.patch > > > 1. a) Connect to zookeeper using zkCli > b) just input space and then hit enter > 2. a) Connect to zookeeper using zkCli and hit enter it will come as > connected > b) just input space and then hit enter > Console log is as below:- > [zk: localhost:2181(CONNECTING) 0] 2016-08-25 16:54:48,143 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxnSocketNetty$ZKClientPipelineFactory@363] > - SSL handler added for channel: null > 2016-08-25 16:54:48,175 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxn$SendThread@980] - Socket > connection established, initiating session, client: /0:0:0:0:0:0:0:1:44592, > server: localhost/0:0:0:0:0:0:0:1:2181 > 2016-08-25 16:54:48,178 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxnSocketNetty$1@146] - channel is > connected: [id: 0xd03f4226, /0:0:0:0:0:0:0:1:44592 => > localhost/0:0:0:0:0:0:0:1:2181] > 2016-08-25 16:54:48,288 [myid:] - INFO [New I/O worker > #1:ClientCnxn$SendThread@1400] - Session establishment complete on server > localhost/0:0:0:0:0:0:0:1:2181, sessionid = 0x101a00305cc0005, negotiated > timeout = 3 > WATCHER:: > WatchedEvent state:SyncConnected type:None path:null > > Exception in thread "main" java.lang.NullPointerException > at > org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.getArgArray(ZooKeeperMain.java:171) > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:613) > at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:577) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:320) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:280) > > After connection is established, input space and hit enter > [zk: localhost:2181(CONNECTING) 0] 2016-08-25 16:56:22,445 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxnSocketNetty$ZKClientPipelineFactory@363] > - SSL handler added for channel: null > 2016-08-25 16:56:22,481 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxn$SendThread@980] - Socket > connection established, initiating session, client: /0:0:0:0:0:0:0:1:44594, > server: localhost/0:0:0:0:0:0:0:1:2181 > 2016-08-25 16:56:22,484 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxnSocketNetty$1@146] - channel is > connected: [id: 0xe6d3a461, /0:0:0:0:0:0:0:1:44594 => > localhost/0:0:0:0:0:0:0:1:2181] > 2016-08-25 16:56:22,597 [myid:] - INFO [New I/O worker > #1:ClientCnxn$SendThread@1400] - Session establishment complete on server > localhost/0:0:0:0:0:0:0:1:2181, sessionid = 0x101a00305cc0007, negotiated > timeout = 3 > WATCHER:: > WatchedEvent state:SyncConnected type:None path:null > [zk: localhost:2181(CONNECTED) 0] > Exception in thread "main" java.lang.NullPointerException > at > org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.getArgArray(ZooKeeperMain.java:171) > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:613) > at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:577) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:320) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:280) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2583) Using one client able to access the znode with localhost but fails from another client when IP ACL is set for znode using 127.0.0.1
Rakesh Kumar Singh created ZOOKEEPER-2583: - Summary: Using one client able to access the znode with localhost but fails from another client when IP ACL is set for znode using 127.0.0.1 Key: ZOOKEEPER-2583 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2583 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.1 Reporter: Rakesh Kumar Singh Priority: Minor Using one client able to access the znode with localhost but fails from another client when IP ACL is set for znode using 127.0.0.1 Start zookeeper in cluster mode. Client 1 :- [zk: localhost:2181(CONNECTED) 11] create /ip_test hello Created /ip_test [zk: localhost:2181(CONNECTED) 12] setAcl /ip_test ip_testip_test4 [zk: localhost:2181(CONNECTED) 12] setAcl /ip_test ip:127.0.0.1:crdwa [zk: localhost:2181(CONNECTED) 13] get /ip_test hello [zk: localhost:2181(CONNECTED) 14] set /ip_test hi [zk: localhost:2181(CONNECTED) 15] Client 2 :- [zk: localhost:2181(CONNECTED) 0] get /ip_test Authentication is not valid : /ip_test [zk: localhost:2181(CONNECTED) 1] getAcl /ip_test 'ip,'127.0.0.1 : cdrwa [zk: localhost:2181(CONNECTED) 2] quit now quit the client connection and connect again using 127.0.0.1 (like :- ./zkCli.sh -server 127.0.0.1:2181) [zk: 127.0.0.1:2181(CONNECTED) 0] get /ip_test hi -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2582) When addauth twice for same user but different password, it is adding 2 digest corresponding to both username, password and so we can able to access znode with user
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490467#comment-15490467 ] Rakesh Kumar Singh commented on ZOOKEEPER-2582: --- It should override from later addauth details > When addauth twice for same user but different password, it is adding 2 > digest corresponding to both username, password and so we can able to access > znode with user and any of these password which does not seem to be correct > > > Key: ZOOKEEPER-2582 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2582 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh > > When addauth twice for same user but different password, it is adding 2 > digest corresponding to both username, password and so we can able to access > znode with user and any of these password which does not seem to be correct > Steps:- > [zk: localhost:2181(CONNECTED) 0] addauth digest user1:pass1 > [zk: localhost:2181(CONNECTED) 1] addauth digest user1:pass > [zk: localhost:2181(CONNECTED) 9] create /user_test5 hello > Created /user_test5 > [zk: localhost:2181(CONNECTED) 10] setAcl /user_test5 auth:user1:pass1:crdwa > [zk: localhost:2181(CONNECTED) 11] getAcl /user_test5 > 'digest,'user1:+7K83PhyQ3ijGj0ADmljf0quVwQ= > : cdrwa > 'digest,'user1:UZIsvOKp29j8vAahJzjgpA1VTOk= > : cdrwa > Here we can see 2 entries for same user (user1) with different password > Now disconnect the client and connect again using zkCli.sh > addauth digest user1:, we can able to access the znode. > [zk: localhost:2181(CONNECTED) 0] get /user_test5 > Authentication is not valid : /user_test5 > [zk: localhost:2181(CONNECTED) 1] addauth digest user1:pass > [zk: localhost:2181(CONNECTED) 2] get /user_test5 > hello > Same way, it will allow n number of entry if we addauth for same user with n > number of password -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2582) When addauth twice for same user but different password, it is adding 2 digest corresponding to both username, password and so we can able to access znode with user a
Rakesh Kumar Singh created ZOOKEEPER-2582: - Summary: When addauth twice for same user but different password, it is adding 2 digest corresponding to both username, password and so we can able to access znode with user and any of these password which does not seem to be correct Key: ZOOKEEPER-2582 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2582 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.1 Reporter: Rakesh Kumar Singh When addauth twice for same user but different password, it is adding 2 digest corresponding to both username, password and so we can able to access znode with user and any of these password which does not seem to be correct Steps:- [zk: localhost:2181(CONNECTED) 0] addauth digest user1:pass1 [zk: localhost:2181(CONNECTED) 1] addauth digest user1:pass [zk: localhost:2181(CONNECTED) 9] create /user_test5 hello Created /user_test5 [zk: localhost:2181(CONNECTED) 10] setAcl /user_test5 auth:user1:pass1:crdwa [zk: localhost:2181(CONNECTED) 11] getAcl /user_test5 'digest,'user1:+7K83PhyQ3ijGj0ADmljf0quVwQ= : cdrwa 'digest,'user1:UZIsvOKp29j8vAahJzjgpA1VTOk= : cdrwa Here we can see 2 entries for same user (user1) with different password Now disconnect the client and connect again using zkCli.sh addauth digest user1:, we can able to access the znode. [zk: localhost:2181(CONNECTED) 0] get /user_test5 Authentication is not valid : /user_test5 [zk: localhost:2181(CONNECTED) 1] addauth digest user1:pass [zk: localhost:2181(CONNECTED) 2] get /user_test5 hello Same way, it will allow n number of entry if we addauth for same user with n number of password -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2581) Not handled NullPointerException while creating key manager and trustManager
Rakesh Kumar Singh created ZOOKEEPER-2581: - Summary: Not handled NullPointerException while creating key manager and trustManager Key: ZOOKEEPER-2581 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2581 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.1 Reporter: Rakesh Kumar Singh Assignee: Rakesh Kumar Singh Not handled NullPointerException while creating key manager and trustManager:- 2016-09-14 13:35:23,488 [myid:1] - ERROR [CommitProcWorkThread-1:X509AuthenticationProvider@78] - Failed to create key manager org.apache.zookeeper.common.X509Exception$KeyManagerException: java.lang.NullPointerException at org.apache.zookeeper.common.X509Util.createKeyManager(X509Util.java:129) at org.apache.zookeeper.server.auth.X509AuthenticationProvider.(X509AuthenticationProvider.java:75) at org.apache.zookeeper.server.auth.ProviderRegistry.initialize(ProviderRegistry.java:42) at org.apache.zookeeper.server.auth.ProviderRegistry.getProvider(ProviderRegistry.java:68) at org.apache.zookeeper.server.PrepRequestProcessor.checkACL(PrepRequestProcessor.java:319) at org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:324) at org.apache.zookeeper.server.quorum.CommitProcessor$CommitWorkRequest.doWork(CommitProcessor.java:296) at org.apache.zookeeper.server.WorkerService$ScheduledWorkRequest.run(WorkerService.java:162) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NullPointerException at org.apache.zookeeper.common.X509Util.createKeyManager(X509Util.java:113) ... 10 more 2016-09-14 13:35:23,489 [myid:1] - ERROR [CommitProcWorkThread-1:X509AuthenticationProvider@90] - Failed to create trust manager org.apache.zookeeper.common.X509Exception$TrustManagerException: java.lang.NullPointerException at org.apache.zookeeper.common.X509Util.createTrustManager(X509Util.java:158) at org.apache.zookeeper.server.auth.X509AuthenticationProvider.(X509AuthenticationProvider.java:87) at org.apache.zookeeper.server.auth.ProviderRegistry.initialize(ProviderRegistry.java:42) at org.apache.zookeeper.server.auth.ProviderRegistry.getProvider(ProviderRegistry.java:68) at org.apache.zookeeper.server.PrepRequestProcessor.checkACL(PrepRequestProcessor.java:319) at org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:324) at org.apache.zookeeper.server.quorum.CommitProcessor$CommitWorkRequest.doWork(CommitProcessor.java:296) at org.apache.zookeeper.server.WorkerService$ScheduledWorkRequest.run(WorkerService.java:162) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NullPointerException at org.apache.zookeeper.common.X509Util.createTrustManager(X509Util.java:143) ... 10 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2580) ErrorMessage is not correct when set IP acl and try to set again from another machine
Rakesh Kumar Singh created ZOOKEEPER-2580: - Summary: ErrorMessage is not correct when set IP acl and try to set again from another machine Key: ZOOKEEPER-2580 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2580 Project: ZooKeeper Issue Type: Bug Components: java client Affects Versions: 3.5.1 Reporter: Rakesh Kumar Singh Priority: Minor set IP acl and try to set again from another machine:- [zk: localhost:2181(CONNECTED) 11] setAcl /ip_test ip:10.18.101.80:crdwa KeeperErrorCode = NoAuth for /ip_test -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ZOOKEEPER-2532) zkCli throwing nullpointerException instead it should provide help when invalid input is entered
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh reassigned ZOOKEEPER-2532: - Assignee: Rakesh Kumar Singh > zkCli throwing nullpointerException instead it should provide help when > invalid input is entered > > > Key: ZOOKEEPER-2532 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2532 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.5.1, 3.5.2 > > Attachments: ZOOKEEPER-2532.patch > > > 1. a) Connect to zookeeper using zkCli > b) just input space and then hit enter > 2. a) Connect to zookeeper using zkCli and hit enter it will come as > connected > b) just input space and then hit enter > Console log is as below:- > [zk: localhost:2181(CONNECTING) 0] 2016-08-25 16:54:48,143 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxnSocketNetty$ZKClientPipelineFactory@363] > - SSL handler added for channel: null > 2016-08-25 16:54:48,175 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxn$SendThread@980] - Socket > connection established, initiating session, client: /0:0:0:0:0:0:0:1:44592, > server: localhost/0:0:0:0:0:0:0:1:2181 > 2016-08-25 16:54:48,178 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxnSocketNetty$1@146] - channel is > connected: [id: 0xd03f4226, /0:0:0:0:0:0:0:1:44592 => > localhost/0:0:0:0:0:0:0:1:2181] > 2016-08-25 16:54:48,288 [myid:] - INFO [New I/O worker > #1:ClientCnxn$SendThread@1400] - Session establishment complete on server > localhost/0:0:0:0:0:0:0:1:2181, sessionid = 0x101a00305cc0005, negotiated > timeout = 3 > WATCHER:: > WatchedEvent state:SyncConnected type:None path:null > > Exception in thread "main" java.lang.NullPointerException > at > org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.getArgArray(ZooKeeperMain.java:171) > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:613) > at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:577) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:320) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:280) > > After connection is established, input space and hit enter > [zk: localhost:2181(CONNECTING) 0] 2016-08-25 16:56:22,445 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxnSocketNetty$ZKClientPipelineFactory@363] > - SSL handler added for channel: null > 2016-08-25 16:56:22,481 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxn$SendThread@980] - Socket > connection established, initiating session, client: /0:0:0:0:0:0:0:1:44594, > server: localhost/0:0:0:0:0:0:0:1:2181 > 2016-08-25 16:56:22,484 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxnSocketNetty$1@146] - channel is > connected: [id: 0xe6d3a461, /0:0:0:0:0:0:0:1:44594 => > localhost/0:0:0:0:0:0:0:1:2181] > 2016-08-25 16:56:22,597 [myid:] - INFO [New I/O worker > #1:ClientCnxn$SendThread@1400] - Session establishment complete on server > localhost/0:0:0:0:0:0:0:1:2181, sessionid = 0x101a00305cc0007, negotiated > timeout = 3 > WATCHER:: > WatchedEvent state:SyncConnected type:None path:null > [zk: localhost:2181(CONNECTED) 0] > Exception in thread "main" java.lang.NullPointerException > at > org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.getArgArray(ZooKeeperMain.java:171) > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:613) > at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:577) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:320) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:280) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2532) zkCli throwing nullpointerException instead it should provide help when invalid input is entered
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2532: -- Attachment: ZOOKEEPER-2532.patch > zkCli throwing nullpointerException instead it should provide help when > invalid input is entered > > > Key: ZOOKEEPER-2532 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2532 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Priority: Minor > Attachments: ZOOKEEPER-2532.patch > > > 1. a) Connect to zookeeper using zkCli > b) just input space and then hit enter > 2. a) Connect to zookeeper using zkCli and hit enter it will come as > connected > b) just input space and then hit enter > Console log is as below:- > [zk: localhost:2181(CONNECTING) 0] 2016-08-25 16:54:48,143 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxnSocketNetty$ZKClientPipelineFactory@363] > - SSL handler added for channel: null > 2016-08-25 16:54:48,175 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxn$SendThread@980] - Socket > connection established, initiating session, client: /0:0:0:0:0:0:0:1:44592, > server: localhost/0:0:0:0:0:0:0:1:2181 > 2016-08-25 16:54:48,178 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxnSocketNetty$1@146] - channel is > connected: [id: 0xd03f4226, /0:0:0:0:0:0:0:1:44592 => > localhost/0:0:0:0:0:0:0:1:2181] > 2016-08-25 16:54:48,288 [myid:] - INFO [New I/O worker > #1:ClientCnxn$SendThread@1400] - Session establishment complete on server > localhost/0:0:0:0:0:0:0:1:2181, sessionid = 0x101a00305cc0005, negotiated > timeout = 3 > WATCHER:: > WatchedEvent state:SyncConnected type:None path:null > > Exception in thread "main" java.lang.NullPointerException > at > org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.getArgArray(ZooKeeperMain.java:171) > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:613) > at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:577) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:320) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:280) > > After connection is established, input space and hit enter > [zk: localhost:2181(CONNECTING) 0] 2016-08-25 16:56:22,445 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxnSocketNetty$ZKClientPipelineFactory@363] > - SSL handler added for channel: null > 2016-08-25 16:56:22,481 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxn$SendThread@980] - Socket > connection established, initiating session, client: /0:0:0:0:0:0:0:1:44594, > server: localhost/0:0:0:0:0:0:0:1:2181 > 2016-08-25 16:56:22,484 [myid:] - INFO > [main-SendThread(localhost:2181):ClientCnxnSocketNetty$1@146] - channel is > connected: [id: 0xe6d3a461, /0:0:0:0:0:0:0:1:44594 => > localhost/0:0:0:0:0:0:0:1:2181] > 2016-08-25 16:56:22,597 [myid:] - INFO [New I/O worker > #1:ClientCnxn$SendThread@1400] - Session establishment complete on server > localhost/0:0:0:0:0:0:0:1:2181, sessionid = 0x101a00305cc0007, negotiated > timeout = 3 > WATCHER:: > WatchedEvent state:SyncConnected type:None path:null > [zk: localhost:2181(CONNECTED) 0] > Exception in thread "main" java.lang.NullPointerException > at > org.apache.zookeeper.ZooKeeperMain$MyCommandOptions.getArgArray(ZooKeeperMain.java:171) > at > org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:613) > at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:577) > at > org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:360) > at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:320) > at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:280) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2537) When provide path for "dataDir" with heading space, it is taking correct path (by trucating space) for snapshot but zookeeper_server.pid is getting created in root
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483680#comment-15483680 ] Rakesh Kumar Singh commented on ZOOKEEPER-2537: --- yes, this is dup of ZOOKEEPER-2536 > When provide path for "dataDir" with heading space, it is taking correct path > (by trucating space) for snapshot but zookeeper_server.pid is getting created > in root (/) folder > -- > > Key: ZOOKEEPER-2537 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2537 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh > Fix For: 3.5.3, 3.6.0 > > Attachments: zkServer.sh.patch > > > Scenario 1 :- > When provide path for "dataDir" with heading space, it is taking correct path > (by trucating space) for snapshot but zookeeper_server.pid is getting created > in root (/) folder > Steps to reproduce:- > 1. Configure the dataDir > dataDir= /home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data > Here there is a space after dataDir= > 2. Start Zookeeper Server > 3. The snapshot is getting created at location mentioned above by truncating > the heading space but > zookeeper_server.pid is getting created at root (/) folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2569) plain password is stored when set individual ACL using digest scheme
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2569: -- Component/s: security > plain password is stored when set individual ACL using digest scheme > > > Key: ZOOKEEPER-2569 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2569 > Project: ZooKeeper > Issue Type: Bug > Components: security >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh > > Plain password is stored when set individual ACL using digest scheme instead > of storing the username and encoded hash string of > [zk: localhost:2181(CONNECTED) 13] addauth digest user:pass > [zk: localhost:2181(CONNECTED) 14] setAcl /newNode digest:user:pass:crdwa > [zk: localhost:2181(CONNECTED) 15] getAcl /newNode > 'digest,'user:pass > : cdrwa > [zk: localhost:2181(CONNECTED) 16] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2569) plain password is stored when set individual ACL using digest scheme
Rakesh Kumar Singh created ZOOKEEPER-2569: - Summary: plain password is stored when set individual ACL using digest scheme Key: ZOOKEEPER-2569 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2569 Project: ZooKeeper Issue Type: Bug Affects Versions: 3.5.1 Reporter: Rakesh Kumar Singh Plain password is stored when set individual ACL using digest scheme instead of storing the username and encoded hash string of [zk: localhost:2181(CONNECTED) 13] addauth digest user:pass [zk: localhost:2181(CONNECTED) 14] setAcl /newNode digest:user:pass:crdwa [zk: localhost:2181(CONNECTED) 15] getAcl /newNode 'digest,'user:pass : cdrwa [zk: localhost:2181(CONNECTED) 16] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2567) Error message is not correct when wrong argument is passed for "reconfig" cmd
Rakesh Kumar Singh created ZOOKEEPER-2567: - Summary: Error message is not correct when wrong argument is passed for "reconfig" cmd Key: ZOOKEEPER-2567 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2567 Project: ZooKeeper Issue Type: Bug Components: java client Reporter: Rakesh Kumar Singh Priority: Minor Error message is not correct when wrong argument is passed for "reconfig" cmd Steps to reproduce:- 1. Start zookeeper in cluster mode 2. use reconfig cmd with wrong argument (pass : instead of ;) [zk: localhost:2181(CONNECTED) 10] reconfig -remove 3 -add 3=10.18.221.194:2888:3888:2181 KeeperErrorCode = BadArguments for Here error message is not complete and informative on client console. The log is as below:- 2016-09-08 18:54:08,701 [myid:1] - INFO [ProcessThread(sid:1 cport:-1)::PrepRequestProcessor@512] - Incremental reconfig 2016-09-08 18:54:08,702 [myid:1] - INFO [ProcessThread(sid:1 cport:-1)::PrepRequestProcessor@843] - Got user-level KeeperException when processing sessionid:0x100299b7eac type:reconfig cxid:0x7 zxid:0x40004 txntype:-1 reqpath:n/a Error Path:Reconfiguration failed Error:KeeperErrorCode = BadArguments for Reconfiguration failed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2565) listquota should display the quota even it is set on parent/child node
Rakesh Kumar Singh created ZOOKEEPER-2565: - Summary: listquota should display the quota even it is set on parent/child node Key: ZOOKEEPER-2565 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2565 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.1 Reporter: Rakesh Kumar Singh Priority: Minor listquota should display the quota even it is set on parent/child node. As of now if we have a parent-child hierarchy for example n1->n2->n3 and quota is set for n2. If we try to get quota details on n1 and n3 using listquota, it says no quota set but if try to set the quota on those nodes it fails saying quota is already set on parent node... So listquota should fetch the quota set on any node in hierarchy with exact path (on which quota is set) even though this api is called on any other node in that hierarchy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2564) No message is prompted when trying to delete quota with different quota option
Rakesh Kumar Singh created ZOOKEEPER-2564: - Summary: No message is prompted when trying to delete quota with different quota option Key: ZOOKEEPER-2564 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2564 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.1 Reporter: Rakesh Kumar Singh Priority: Minor No message is prompted when trying to delete quota with different quota option. Steps to reproduce:- 1. Start zookeeper in cluster mode 2. Create some node and set quota like setquota -n 10 /test 3. Now try to delete as below:- delquota -b /test Here no message/exception is prompted. We should prompt message like "Byte Quota does not exist for /test" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2563) delquota -[n|b] is not deleting the set quota properly
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2563: -- Description: delquota -[n|b] is not deleting the set quota properly Steps to reproduce:- 1. Start zookeeper in cluster mode (ssl) 2. create some node say /test 3. Run command as listquota says (as expected) quota for /test does not exist 4. setquota let say setquota -n 10 /test 5. Now try to delete this as below delquota -n /test 6. now check the quota [zk: localhost:2181(CONNECTED) 1] listquota /test absolute path is /zookeeper/quota/test/zookeeper_limits Output quota for /test count=-1,bytes=-1 Output stat for /test count=1,bytes=5 7. Here it is not deleted quota node for test 8. Now try to set some new quota It fails as it is not deleted correctly while delete [zk: localhost:2181(CONNECTED) 3] setquota -n 11 /test Command failed: java.lang.IllegalArgumentException: /test has a parent /zookeeper/quota/test which has a quota But through delquota it is able to delete was: delquota -[n|b] is not deleting the set quota properly Steps to reproduce:- 1. Start zookeeper in cluster mode (ssl) 2. create some node say /test 3. Run command as listquota says (as expected) quota for /test does not exist 4. setquota let say setquota -n 10 /test 5. Now try to delete this as below delquota -n /test 6. now check the quota [zk: localhost:2181(CONNECTED) 1] listquota /test absolute path is /zookeeper/quota/test/zookeeper_limits Output quota for /test count=-1,bytes=-1 Output stat for /test count=1,bytes=5 7. Here it is not deleted quota node for test 8. Now try to set some new quota It fails as it is not deleted correctly while delete [zk: localhost:2181(CONNECTED) 3] setquota -n 11 /test Command failed: java.lang.IllegalArgumentException: /test has a parent /zookeeper/quota/test which has a quota > delquota -[n|b] is not deleting the set quota properly > -- > > Key: ZOOKEEPER-2563 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2563 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh > > delquota -[n|b] is not deleting the set quota properly > Steps to reproduce:- > 1. Start zookeeper in cluster mode (ssl) > 2. create some node say /test > 3. Run command as listquota says (as expected) > quota for /test does not exist > 4. setquota let say > setquota -n 10 /test > 5. Now try to delete this as below > delquota -n /test > 6. now check the quota > [zk: localhost:2181(CONNECTED) 1] listquota /test > absolute path is /zookeeper/quota/test/zookeeper_limits > Output quota for /test count=-1,bytes=-1 > Output stat for /test count=1,bytes=5 > 7. Here it is not deleted quota node for test > 8. Now try to set some new quota > It fails as it is not deleted correctly while delete > [zk: localhost:2181(CONNECTED) 3] setquota -n 11 /test > Command failed: java.lang.IllegalArgumentException: /test has a parent > /zookeeper/quota/test which has a quota > But through delquota it is able to delete -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2563) delquota -[n|b] is not deleting the set quota properly
Rakesh Kumar Singh created ZOOKEEPER-2563: - Summary: delquota -[n|b] is not deleting the set quota properly Key: ZOOKEEPER-2563 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2563 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.1 Reporter: Rakesh Kumar Singh delquota -[n|b] is not deleting the set quota properly Steps to reproduce:- 1. Start zookeeper in cluster mode (ssl) 2. create some node say /test 3. Run command as listquota says (as expected) quota for /test does not exist 4. setquota let say setquota -n 10 /test 5. Now try to delete this as below delquota -n /test 6. now check the quota [zk: localhost:2181(CONNECTED) 1] listquota /test absolute path is /zookeeper/quota/test/zookeeper_limits Output quota for /test count=-1,bytes=-1 Output stat for /test count=1,bytes=5 7. Here it is not deleted quota node for test 8. Now try to set some new quota It fails as it is not deleted correctly while delete [zk: localhost:2181(CONNECTED) 3] setquota -n 11 /test Command failed: java.lang.IllegalArgumentException: /test has a parent /zookeeper/quota/test which has a quota -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2539) Throwing nullpointerException when run the command "config -c" when client port is mentioned as separate and not like new style
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15472859#comment-15472859 ] Rakesh Kumar Singh commented on ZOOKEEPER-2539: --- Thank you for feedback !!! > Throwing nullpointerException when run the command "config -c" when client > port is mentioned as separate and not like new style > --- > > Key: ZOOKEEPER-2539 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2539 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.5.3, 3.6.0 > > Attachments: ConfigUtils.java.patch, ConfigUtils.java.patch, > ZOOKEEPER-2539.patch > > > Throwing nullpointerException when run the command "config -c" when client > port is mentioned as separate and not like new style > 1. Configure the zookeeper to start in cluster mode like below- > clientPort=2181 > server.1=10.18.101.80:2888:3888 > server.2=10.18.219.50:2888:3888 > server.3=10.18.221.194:2888:3888 > and not like below:- > server.1=10.18.101.80:2888:3888:participant;2181 > server.2=10.18.219.50:2888:3888:participant;2181 > server.3=10.18.221.194:2888:3888:participant;2181 > 2. Start the cluster and one client using >zkCli.sh > 3. execute command "config -c" > It is throwing nullpointerException:- > root@BLR110865:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin# > ./zkCli.sh > Connecting to localhost:2181 > 2016-08-29 21:45:19,558 [myid:] - INFO [main:Environment@109] - Client > environment:zookeeper.version=3.5.1-alpha--1, built on 08/18/2016 08:20 GMT > 2016-08-29 21:45:19,561 [myid:] - INFO [main:Environment@109] - Client > environment:host.name=BLR110865 > 2016-08-29 21:45:19,562 [myid:] - INFO [main:Environment@109] - Client > environment:java.version=1.7.0_17 > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.vendor=Oracle Corporation > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.home=/usr/lib/jvm/oracle_jdk7/jre > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.class.path=/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../build/classes:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../build/lib/*.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/slf4j-log4j12-1.7.5.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/slf4j-api-1.7.5.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/servlet-api-2.5-20081211.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/netty-3.7.0.Final.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/log4j-1.2.16.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jline-2.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jetty-util-6.1.26.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jetty-6.1.26.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/javacc.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jackson-mapper-asl-1.9.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jackson-core-asl-1.9.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/commons-cli-1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/ant-eclipse-1.0-jvm1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../zookeeper-3.5.1-alpha.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../src/java/lib/ant-eclipse-1.0-jvm1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../conf: > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.library.path=/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.io.tmpdir=/tmp > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.compiler= > 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client > environment:os.name=Linux > 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client > environment:os.arch=amd64 > 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client > environment:os.version=4.4.0-31-generic > 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client > environment:user.name=root > 2016-08-29
[jira] [Commented] (ZOOKEEPER-2536) When provide path for "dataDir" with trailing space, it is taking correct path (by trucating space) for snapshot but creating temporary file with some junk folder n
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15472858#comment-15472858 ] Rakesh Kumar Singh commented on ZOOKEEPER-2536: --- Thank you for feedback and commit !!! > When provide path for "dataDir" with trailing space, it is taking correct > path (by trucating space) for snapshot but creating temporary file with some > junk folder name for zookeeper_server.pid > > > Key: ZOOKEEPER-2536 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2536 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh >Assignee: Rakesh Kumar Singh > Fix For: 3.5.3, 3.6.0 > > Attachments: zkServer.sh.patch, zkServer.sh.patch > > > Scenario 1:- > When provide path for "dataDir" with trailing space, it is taking correct > path (by trucating space) for snapshot but creating temporary file with some > junk folder name for zookeeper_server.pid > Steps to reproduce:- > 1. Configure the dataDir > dataDir=/home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data > Here there is a space after /data > 2. Start Zookeeper Server > 3. The snapshot is getting created at location mentioned above by truncating > the trailing space but > one temp folder with junk name (like -> D29D4X~J) is getting created for > zookeeper_server.pid > Scenario 2:- > When configure the heading and trailing space in above mentioned scenario. > the temp folder is getting created in zookeeper/bin folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2559) Failed to delete the set quota for ephemeral node when the node is deleted because of client session closed
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15470461#comment-15470461 ] Rakesh Kumar Singh commented on ZOOKEEPER-2559: --- Even for normal node also when the node is deleted the set quota remained as it is and not getting deleted. > Failed to delete the set quota for ephemeral node when the node is deleted > because of client session closed > --- > > Key: ZOOKEEPER-2559 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2559 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh > > Failed to delete the set quota for ephemeral node when the node is deleted > because of client session closed > [zk: localhost:2181(CONNECTED) 0] create -e /e_test hello > Created /e_test > [zk: localhost:2181(CONNECTED) 1] setquota -n 10 /e_test > [zk: localhost:2181(CONNECTED) 2] listquota /e_test > absolute path is /zookeeper/quota/e_test/zookeeper_limits > Output quota for /e_test count=10,bytes=-1 > Output stat for /e_test count=1,bytes=5 > Now close the client connection and so the ephemeral node gets deleted. But > the corresponding quota is not getting deleted as below:- > [zk: localhost:2181(CONNECTED) 0] ls / > [test, test1, test3, zookeeper] > [zk: localhost:2181(CONNECTED) 1] listquota /e_test > absolute path is /zookeeper/quota/e_test/zookeeper_limits > Output quota for /e_test count=10,bytes=-1 > Output stat for /e_test count=0,bytes=0 > [zk: localhost:2181(CONNECTED) 2] > and so now again create the ephemeral node with same node and try to set the > quota, it will fail. > [zk: localhost:2181(CONNECTED) 2] create -e /e_test hello > Created /e_test > [zk: localhost:2181(CONNECTED) 3] setquota -n 10 /e_test > Command failed: java.lang.IllegalArgumentException: /e_test has a parent > /zookeeper/quota/e_test which has a quota > [zk: localhost:2181(CONNECTED) 4] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2559) Failed to delete the set quota for ephemeral node when the node is deleted because of client session closed
Rakesh Kumar Singh created ZOOKEEPER-2559: - Summary: Failed to delete the set quota for ephemeral node when the node is deleted because of client session closed Key: ZOOKEEPER-2559 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2559 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.2, 3.5.1 Reporter: Rakesh Kumar Singh Failed to delete the set quota for ephemeral node when the node is deleted because of client session closed [zk: localhost:2181(CONNECTED) 0] create -e /e_test hello Created /e_test [zk: localhost:2181(CONNECTED) 1] setquota -n 10 /e_test [zk: localhost:2181(CONNECTED) 2] listquota /e_test absolute path is /zookeeper/quota/e_test/zookeeper_limits Output quota for /e_test count=10,bytes=-1 Output stat for /e_test count=1,bytes=5 Now close the client connection and so the ephemeral node gets deleted. But the corresponding quota is not getting deleted as below:- [zk: localhost:2181(CONNECTED) 0] ls / [test, test1, test3, zookeeper] [zk: localhost:2181(CONNECTED) 1] listquota /e_test absolute path is /zookeeper/quota/e_test/zookeeper_limits Output quota for /e_test count=10,bytes=-1 Output stat for /e_test count=0,bytes=0 [zk: localhost:2181(CONNECTED) 2] and so now again create the ephemeral node with same node and try to set the quota, it will fail. [zk: localhost:2181(CONNECTED) 2] create -e /e_test hello Created /e_test [zk: localhost:2181(CONNECTED) 3] setquota -n 10 /e_test Command failed: java.lang.IllegalArgumentException: /e_test has a parent /zookeeper/quota/e_test which has a quota [zk: localhost:2181(CONNECTED) 4] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2556) peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2556: -- Description: peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime Steps to reproduce:- 1. Start zookeeper in cluster with one node as observer by configuring peerType=observer in zoo.cfg and server.2=10.18.219.50:2888:3888:observer;2181 2. Start the cluster 3. start a client and change the node from observer to participant, the configuration related to peertype remained same though other things like clientport got from zoo.cfg >reconfig -remove 2 -add 2=10.18.219.50:2888:3888:participant;2181 We should either remove this parameter or update with correct node type at run time was: peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime Steps to reproduce:- 1. Start zookeeper in cluster with one node as observer by configuring peerType=observer in zoo.cfg and server.2=10.18.219.50:2888:3888:observer;2181 2. Start the cluster 3. start a client and change the node from observer to participant, the configuration related to peertype remained same though other things like clientport got from zoo.cfg We should either remove this parameter or update with correct node type at run time > peerType remains as "observer" in zoo.cfg even though we change the node from > observer to participant runtime > - > > Key: ZOOKEEPER-2556 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2556 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Priority: Minor > > peerType remains as "observer" in zoo.cfg even though we change the node from > observer to participant runtime > Steps to reproduce:- > 1. Start zookeeper in cluster with one node as observer by configuring > peerType=observer in zoo.cfg and server.2=10.18.219.50:2888:3888:observer;2181 > 2. Start the cluster > 3. start a client and change the node from observer to participant, the > configuration related to peertype remained same though other things like > clientport got from zoo.cfg > >reconfig -remove 2 -add 2=10.18.219.50:2888:3888:participant;2181 > We should either remove this parameter or update with correct node type at > run time -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2556) peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime
Rakesh Kumar Singh created ZOOKEEPER-2556: - Summary: peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime Key: ZOOKEEPER-2556 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2556 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.1 Reporter: Rakesh Kumar Singh Priority: Minor peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime Steps to reproduce:- 1. Start zookeeper in cluster with one node as observer by configuring peerType=observer in zoo.cfg and server.2=10.18.219.50:2888:3888:observer;2181 2. Start the cluster 3. start a client and change the node from observer to participant, the configuration related to peertype remained same though other things like clientport got from zoo.cfg We should either remove this parameter or update with correct node type at run time -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2555) zookeeper started in observer mode takes long time to come to observer state once leader restarted and so client connected to observer mode has to wait for longer tim
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh Kumar Singh updated ZOOKEEPER-2555:
--
Description:
zookeeper started in observer mode takes long time (some times 25 seconds) to
come to observer state once leader restarted and so client connected to
observer mode has to wait for longer time to get service
Steps to reproduce:-
1. Start zookeeper in cluster mode in which one node is in observer mode
2. stop the leader node (some times we need to wait for 30 secs to reproduce
this issue)
3. Start the leader node
4. Check the observer node status -
It will be in
"Error contacting service. It is probably not running."
and takes long time (25 secs) to come to observer mode. And hence client
connected to this node will not get service during this time.
Log at observer node is as below:-
2016-09-06 17:49:14,774 [myid:2] - WARN
[WorkerSender[myid=2]:QuorumCnxManager@459] - Cannot open channel to 3 at
election address /10.18.221.194:3888
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
at java.net.Socket.connect(Socket.java:579)
at
org.apache.zookeeper.server.quorum.QuorumCnxManager.connectOne(QuorumCnxManager.java:444)
at
org.apache.zookeeper.server.quorum.QuorumCnxManager.connectOne(QuorumCnxManager.java:485)
at
org.apache.zookeeper.server.quorum.QuorumCnxManager.toSend(QuorumCnxManager.java:421)
at
org.apache.zookeeper.server.quorum.FastLeaderElection$Messenger$WorkerSender.process(FastLeaderElection.java:486)
at
org.apache.zookeeper.server.quorum.FastLeaderElection$Messenger$WorkerSender.run(FastLeaderElection.java:465)
at java.lang.Thread.run(Thread.java:722)
{color:red}2016-09-06 17:49:14,776 [myid:2] - INFO
[WorkerReceiver[myid=2]:FastLeaderElection@688] - Notification: 2 (message
format version), 3 (n.leader), 0x2a0001 (n.zxid), 0x7 (n.round), LOOKING
(n.state), 1 (n.sid), 0x2b (n.peerEPoch), LOOKING (my state)1 (n.config
version)
2016-09-06 17:49:40,377 [myid:2] - INFO
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):FastLeaderElection@928]
- Notification time out: 51200 {color}
2016-09-06 17:49:40,378 [myid:2] - INFO
[WorkerSender[myid=2]:QuorumCnxManager@278] - Have smaller server identifier,
so dropping the connection: (3, 2)
2016-09-06 17:49:40,379 [myid:2] - INFO
[WorkerReceiver[myid=2]:FastLeaderElection@688] - Notification: 2 (message
format version), 3 (n.leader), 0x2a0001 (n.zxid), 0x7 (n.round), FOLLOWING
(n.state), 1 (n.sid), 0x2c (n.peerEPoch), LOOKING (my state)1 (n.config
version)
2016-09-06 17:49:40,381 [myid:2] - INFO
[/10.18.219.50:3888:QuorumCnxManager$Listener@637] - Received connection
request /10.18.221.194:34085
2016-09-06 17:49:40,388 [myid:2] - INFO
[WorkerReceiver[myid=2]:FastLeaderElection@688] - Notification: 2 (message
format version), 3 (n.leader), 0x2a0001 (n.zxid), 0x7 (n.round), LEADING
(n.state), 3 (n.sid), 0x2c (n.peerEPoch), LOOKING (my state)1 (n.config
version)
2016-09-06 17:49:40,388 [myid:2] - INFO
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):MBeanRegistry@119]
- Unregister MBean
[org.apache.ZooKeeperService:name0=ReplicatedServer_id2,name1=replica.2,name2=LeaderElection]
2016-09-06 17:49:40,389 [myid:2] - INFO
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):QuorumPeer@1049]
- OBSERVING
2016-09-06 17:49:40,389 [myid:2] - INFO
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@858]
- minSessionTimeout set to 4000
2016-09-06 17:49:40,389 [myid:2] - INFO
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@867]
- maxSessionTimeout set to 4
2016-09-06 17:49:40,389 [myid:2] - INFO
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@156]
- Created server with tickTime 2000 minSessionTimeout 4000 maxSessionTimeout
4 datadir
/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/data/version-2
snapdir
/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/data/version-2
2016-09-06 17:49:40,389 [myid:2] - INFO
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ObserverZooKeeperServer@56]
- syncEnabled =true
2016-09-06 17:49:40,389 [myid:2] - INFO
[QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):Observer@72]
- Observing /10.18.221.194:2888
2016-09-06 17:49:40,396 [myid:2] - INFO
[jira] [Created] (ZOOKEEPER-2555) zookeeper started in observer mode takes long time to come to observer state once leader restarted and so client connected to observer mode has to wait for longer tim
Rakesh Kumar Singh created ZOOKEEPER-2555: - Summary: zookeeper started in observer mode takes long time to come to observer state once leader restarted and so client connected to observer mode has to wait for longer time to get service Key: ZOOKEEPER-2555 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2555 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.1 Reporter: Rakesh Kumar Singh zookeeper started in observer mode takes long time (some times 25 seconds) to come to observer state once leader restarted and so client connected to observer mode has to wait for longer time to get service Steps to reproduce:- 1. Start zookeeper in cluster mode in which one node is in observer mode 2. stop the leader node (some times we need to wait for 30 secs to reproduce this issue) 3. Start the leader node 4. Check the observer node status - It will be in "Error contacting service. It is probably not running." and takes long time (25 secs) to come to observer mode. And hence client connected to this node will not get service during this time. Log at observer node is as below:- 2016-09-06 17:49:14,774 [myid:2] - WARN [WorkerSender[myid=2]:QuorumCnxManager@459] - Cannot open channel to 3 at election address /10.18.221.194:3888 java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391) at java.net.Socket.connect(Socket.java:579) at org.apache.zookeeper.server.quorum.QuorumCnxManager.connectOne(QuorumCnxManager.java:444) at org.apache.zookeeper.server.quorum.QuorumCnxManager.connectOne(QuorumCnxManager.java:485) at org.apache.zookeeper.server.quorum.QuorumCnxManager.toSend(QuorumCnxManager.java:421) at org.apache.zookeeper.server.quorum.FastLeaderElection$Messenger$WorkerSender.process(FastLeaderElection.java:486) at org.apache.zookeeper.server.quorum.FastLeaderElection$Messenger$WorkerSender.run(FastLeaderElection.java:465) at java.lang.Thread.run(Thread.java:722) 2016-09-06 17:49:14,776 [myid:2] - INFO [WorkerReceiver[myid=2]:FastLeaderElection@688] - Notification: 2 (message format version), 3 (n.leader), 0x2a0001 (n.zxid), 0x7 (n.round), LOOKING (n.state), 1 (n.sid), 0x2b (n.peerEPoch), LOOKING (my state)1 (n.config version) 2016-09-06 17:49:40,377 [myid:2] - INFO [QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):FastLeaderElection@928] - Notification time out: 51200 2016-09-06 17:49:40,378 [myid:2] - INFO [WorkerSender[myid=2]:QuorumCnxManager@278] - Have smaller server identifier, so dropping the connection: (3, 2) 2016-09-06 17:49:40,379 [myid:2] - INFO [WorkerReceiver[myid=2]:FastLeaderElection@688] - Notification: 2 (message format version), 3 (n.leader), 0x2a0001 (n.zxid), 0x7 (n.round), FOLLOWING (n.state), 1 (n.sid), 0x2c (n.peerEPoch), LOOKING (my state)1 (n.config version) 2016-09-06 17:49:40,381 [myid:2] - INFO [/10.18.219.50:3888:QuorumCnxManager$Listener@637] - Received connection request /10.18.221.194:34085 2016-09-06 17:49:40,388 [myid:2] - INFO [WorkerReceiver[myid=2]:FastLeaderElection@688] - Notification: 2 (message format version), 3 (n.leader), 0x2a0001 (n.zxid), 0x7 (n.round), LEADING (n.state), 3 (n.sid), 0x2c (n.peerEPoch), LOOKING (my state)1 (n.config version) 2016-09-06 17:49:40,388 [myid:2] - INFO [QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):MBeanRegistry@119] - Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id2,name1=replica.2,name2=LeaderElection] 2016-09-06 17:49:40,389 [myid:2] - INFO [QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):QuorumPeer@1049] - OBSERVING 2016-09-06 17:49:40,389 [myid:2] - INFO [QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@858] - minSessionTimeout set to 4000 2016-09-06 17:49:40,389 [myid:2] - INFO [QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@867] - maxSessionTimeout set to 4 2016-09-06 17:49:40,389 [myid:2] - INFO [QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@156] - Created server with tickTime 2000 minSessionTimeout 4000 maxSessionTimeout 4 datadir /home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/data/version-2 snapdir /home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/data/version-2 2016-09-06 17:49:40,389 [myid:2] - INFO
[jira] [Created] (ZOOKEEPER-2546) Started throwing "Error Path:null Error:KeeperErrorCode = ReconfigInProgress" error when trying to change the cluster using reconfig and the IO hangged at one node
Rakesh Kumar Singh created ZOOKEEPER-2546: - Summary: Started throwing "Error Path:null Error:KeeperErrorCode = ReconfigInProgress" error when trying to change the cluster using reconfig and the IO hangged at one node Key: ZOOKEEPER-2546 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2546 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.1 Reporter: Rakesh Kumar Singh Started throwing "Error Path:null Error:KeeperErrorCode = ReconfigInProgress" error when trying to change the cluster using reconfig and the IO hangged at one node. Steps:- 1. Start Zookeeper in cluster mode 2. try to reconfig the cluster using "reconfig" command from one node's client (194) like "reconfig -remove 3 -add 3=10.18.221.194:2888:3888;2181 3. make the IO busy for 5-10 secs at 194 node and then release 4. Again execute the above reconfig command It is failing to execute even after 3-4 mins. Server log is attached. (Complete server log is attached) 2016-09-02 18:12:05,845 [myid:2] - INFO [QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):QuorumPeer@1074] - LEADING 2016-09-02 18:12:05,848 [myid:2] - INFO [QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):Leader@63] - TCP NoDelay set to: true 2016-09-02 18:12:05,848 [myid:2] - INFO [QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):Leader@83] - zookeeper.leader.maxConcurrentSnapshots = 10 2016-09-02 18:12:05,848 [myid:2] - INFO [QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):Leader@85] - zookeeper.leader.maxConcurrentSnapshotTimeout = 5 2016-09-02 18:12:05,849 [myid:2] - INFO [QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@858] - minSessionTimeout set to 4000 2016-09-02 18:12:05,849 [myid:2] - INFO [QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@867] - maxSessionTimeout set to 4 2016-09-02 18:12:05,849 [myid:2] - INFO [QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ZooKeeperServer@156] - Created server with tickTime 2000 minSessionTimeout 4000 maxSessionTimeout 4 datadir /home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/data/version-2 snapdir /home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/data/version-2 2016-09-02 18:12:05,850 [myid:2] - INFO [QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):Leader@412] - LEADING - LEADER ELECTION TOOK - 5 2016-09-02 18:12:05,852 [myid:2] - INFO [QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):FileTxnSnapLog@298] - Snapshotting: 0x10001 to /home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/data/version-2/snapshot.10001 2016-09-02 18:12:06,854 [myid:2] - INFO [LearnerHandler-/10.18.101.80:55632:LearnerHandler@382] - Follower sid: 1 : info : 10.18.101.80:2888:3888:participant;0.0.0.0:2181 2016-09-02 18:12:06,869 [myid:2] - INFO [LearnerHandler-/10.18.101.80:55632:LearnerHandler@683] - Synchronizing with Follower sid: 1 maxCommittedLog=0x10001 minCommittedLog=0x10001 lastProcessedZxid=0x10001 peerLastZxid=0x10001 2016-09-02 18:12:06,869 [myid:2] - INFO [LearnerHandler-/10.18.101.80:55632:LearnerHandler@727] - Sending DIFF zxid=0x10001 for peer sid: 1 2016-09-02 18:12:06,888 [myid:2] - INFO [QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):Leader@1245] - Have quorum of supporters, sids: [ [1, 2] ]; starting up and setting last processed zxid: 0x2 2016-09-02 18:12:06,890 [myid:2] - INFO [QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):CommitProcessor@254] - Configuring CommitProcessor with 8 worker threads. 2016-09-02 18:12:06,898 [myid:2] - INFO [QuorumPeer[myid=2](plain=/0:0:0:0:0:0:0:0:2181)(secure=disabled):ContainerManager@64] - Using checkIntervalMs=6 maxPerMinute=1 2016-09-02 18:12:18,886 [myid:2] - INFO [WorkerReceiver[myid=2]:FastLeaderElection@688] - Notification: 2 (message format version), 3 (n.leader), 0x0 (n.zxid), 0x (n.round), LEADING (n.state), 3 (n.sid), 0x1 (n.peerEPoch), LEADING (my state)20028 (n.config version) 2016-09-02 18:13:47,869 [myid:2] - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@512] - Incremental reconfig 2016-09-02 18:13:47,872 [myid:2] - ERROR [ProcessThread(sid:2 cport:-1)::QuorumPeer@1383] - setLastSeenQuorumVerifier called with stale config 8589934593. Current version: 8589934632 2016-09-02 18:14:15,545 [myid:2] - INFO [ProcessThread(sid:2 cport:-1)::PrepRequestProcessor@843] - Got user-level KeeperException when processing sessionid:0x1000aa5ce65 type:reconfig cxid:0x3 zxid:0x20002 txntype:-1 reqpath:n/a Error Path:null Error:KeeperErrorCode = ReconfigInProgress 2016-09-02 18:14:56,442 [myid:2] - INFO
[jira] [Updated] (ZOOKEEPER-2539) Throwing nullpointerException when run the command "config -c" when client port is mentioned as separate and not like new style
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2539: -- Attachment: ConfigUtils.java.patch > Throwing nullpointerException when run the command "config -c" when client > port is mentioned as separate and not like new style > --- > > Key: ZOOKEEPER-2539 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2539 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.5.1, 3.5.2 > > Attachments: ConfigUtils.java.patch, ConfigUtils.java.patch > > > Throwing nullpointerException when run the command "config -c" when client > port is mentioned as separate and not like new style > 1. Configure the zookeeper to start in cluster mode like below- > clientPort=2181 > server.1=10.18.101.80:2888:3888 > server.2=10.18.219.50:2888:3888 > server.3=10.18.221.194:2888:3888 > and not like below:- > server.1=10.18.101.80:2888:3888:participant;2181 > server.2=10.18.219.50:2888:3888:participant;2181 > server.3=10.18.221.194:2888:3888:participant;2181 > 2. Start the cluster and one client using >zkCli.sh > 3. execute command "config -c" > It is throwing nullpointerException:- > root@BLR110865:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin# > ./zkCli.sh > Connecting to localhost:2181 > 2016-08-29 21:45:19,558 [myid:] - INFO [main:Environment@109] - Client > environment:zookeeper.version=3.5.1-alpha--1, built on 08/18/2016 08:20 GMT > 2016-08-29 21:45:19,561 [myid:] - INFO [main:Environment@109] - Client > environment:host.name=BLR110865 > 2016-08-29 21:45:19,562 [myid:] - INFO [main:Environment@109] - Client > environment:java.version=1.7.0_17 > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.vendor=Oracle Corporation > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.home=/usr/lib/jvm/oracle_jdk7/jre > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.class.path=/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../build/classes:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../build/lib/*.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/slf4j-log4j12-1.7.5.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/slf4j-api-1.7.5.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/servlet-api-2.5-20081211.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/netty-3.7.0.Final.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/log4j-1.2.16.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jline-2.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jetty-util-6.1.26.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jetty-6.1.26.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/javacc.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jackson-mapper-asl-1.9.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jackson-core-asl-1.9.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/commons-cli-1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/ant-eclipse-1.0-jvm1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../zookeeper-3.5.1-alpha.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../src/java/lib/ant-eclipse-1.0-jvm1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../conf: > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.library.path=/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.io.tmpdir=/tmp > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.compiler= > 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client > environment:os.name=Linux > 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client > environment:os.arch=amd64 > 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client > environment:os.version=4.4.0-31-generic > 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client > environment:user.name=root > 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client > environment:user.home=/root >
[jira] [Updated] (ZOOKEEPER-2536) When provide path for "dataDir" with trailing space, it is taking correct path (by trucating space) for snapshot but creating temporary file with some junk folder nam
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2536: -- Attachment: zkServer.sh.patch > When provide path for "dataDir" with trailing space, it is taking correct > path (by trucating space) for snapshot but creating temporary file with some > junk folder name for zookeeper_server.pid > > > Key: ZOOKEEPER-2536 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2536 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh > Fix For: 3.5.1, 3.5.2 > > Attachments: zkServer.sh.patch, zkServer.sh.patch > > > Scenario 1:- > When provide path for "dataDir" with trailing space, it is taking correct > path (by trucating space) for snapshot but creating temporary file with some > junk folder name for zookeeper_server.pid > Steps to reproduce:- > 1. Configure the dataDir > dataDir=/home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data > Here there is a space after /data > 2. Start Zookeeper Server > 3. The snapshot is getting created at location mentioned above by truncating > the trailing space but > one temp folder with junk name (like -> D29D4X~J) is getting created for > zookeeper_server.pid > Scenario 2:- > When configure the heading and trailing space in above mentioned scenario. > the temp folder is getting created in zookeeper/bin folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2545) Keep maintaining the old zoo.cfg.dynamic* files which will keep eating system memory which is getting generated as part of reconfig execution
Rakesh Kumar Singh created ZOOKEEPER-2545: - Summary: Keep maintaining the old zoo.cfg.dynamic* files which will keep eating system memory which is getting generated as part of reconfig execution Key: ZOOKEEPER-2545 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2545 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.1 Reporter: Rakesh Kumar Singh Keep maintaining the old zoo.cfg.dynamic* files which will be getting created every time when "reconfig" is executed Steps to reproduce:-1 1. Setup the zookeeper in cluster mode and start 2. trying running reconfig command like >reconfig -remove 3 -add 1=10.18.101.80:2888:3888;2181 3. It will create new zoo.cfg.dynamic in conf folder The problem is it is not deleting the old zoo.cfg.dynamic* files which will keep eating the memory -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2544) " unary operator expected" message on the console while trying to get the zookeeper status
Rakesh Kumar Singh created ZOOKEEPER-2544: - Summary: " unary operator expected" message on the console while trying to get the zookeeper status Key: ZOOKEEPER-2544 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2544 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.2, 3.5.1 Reporter: Rakesh Kumar Singh Priority: Minor root@BLR110865:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin# ./zkServer.sh status ZooKeeper JMX enabled by default Using config: /home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../conf/zoo.cfg ./zkServer.sh: line 223: [: =: unary operator expected -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2536) When provide path for "dataDir" with trailing space, it is taking correct path (by trucating space) for snapshot but creating temporary file with some junk folder n
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457523#comment-15457523 ] Rakesh Kumar Singh commented on ZOOKEEPER-2536: --- thank you for review, i will upload again. > When provide path for "dataDir" with trailing space, it is taking correct > path (by trucating space) for snapshot but creating temporary file with some > junk folder name for zookeeper_server.pid > > > Key: ZOOKEEPER-2536 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2536 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh > Fix For: 3.5.1, 3.5.2 > > Attachments: zkServer.sh.patch > > > Scenario 1:- > When provide path for "dataDir" with trailing space, it is taking correct > path (by trucating space) for snapshot but creating temporary file with some > junk folder name for zookeeper_server.pid > Steps to reproduce:- > 1. Configure the dataDir > dataDir=/home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data > Here there is a space after /data > 2. Start Zookeeper Server > 3. The snapshot is getting created at location mentioned above by truncating > the trailing space but > one temp folder with junk name (like -> D29D4X~J) is getting created for > zookeeper_server.pid > Scenario 2:- > When configure the heading and trailing space in above mentioned scenario. > the temp folder is getting created in zookeeper/bin folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2539) Throwing nullpointerException when run the command "config -c" when client port is mentioned as separate and not like new style
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15457525#comment-15457525 ] Rakesh Kumar Singh commented on ZOOKEEPER-2539: --- Thanks for feedback, will make the changes and upload the same. > Throwing nullpointerException when run the command "config -c" when client > port is mentioned as separate and not like new style > --- > > Key: ZOOKEEPER-2539 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2539 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh >Priority: Minor > Fix For: 3.5.1, 3.5.2 > > Attachments: ConfigUtils.java.patch > > > Throwing nullpointerException when run the command "config -c" when client > port is mentioned as separate and not like new style > 1. Configure the zookeeper to start in cluster mode like below- > clientPort=2181 > server.1=10.18.101.80:2888:3888 > server.2=10.18.219.50:2888:3888 > server.3=10.18.221.194:2888:3888 > and not like below:- > server.1=10.18.101.80:2888:3888:participant;2181 > server.2=10.18.219.50:2888:3888:participant;2181 > server.3=10.18.221.194:2888:3888:participant;2181 > 2. Start the cluster and one client using >zkCli.sh > 3. execute command "config -c" > It is throwing nullpointerException:- > root@BLR110865:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin# > ./zkCli.sh > Connecting to localhost:2181 > 2016-08-29 21:45:19,558 [myid:] - INFO [main:Environment@109] - Client > environment:zookeeper.version=3.5.1-alpha--1, built on 08/18/2016 08:20 GMT > 2016-08-29 21:45:19,561 [myid:] - INFO [main:Environment@109] - Client > environment:host.name=BLR110865 > 2016-08-29 21:45:19,562 [myid:] - INFO [main:Environment@109] - Client > environment:java.version=1.7.0_17 > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.vendor=Oracle Corporation > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.home=/usr/lib/jvm/oracle_jdk7/jre > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.class.path=/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../build/classes:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../build/lib/*.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/slf4j-log4j12-1.7.5.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/slf4j-api-1.7.5.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/servlet-api-2.5-20081211.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/netty-3.7.0.Final.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/log4j-1.2.16.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jline-2.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jetty-util-6.1.26.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jetty-6.1.26.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/javacc.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jackson-mapper-asl-1.9.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jackson-core-asl-1.9.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/commons-cli-1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/ant-eclipse-1.0-jvm1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../zookeeper-3.5.1-alpha.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../src/java/lib/ant-eclipse-1.0-jvm1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../conf: > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.library.path=/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.io.tmpdir=/tmp > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.compiler= > 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client > environment:os.name=Linux > 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client > environment:os.arch=amd64 > 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client > environment:os.version=4.4.0-31-generic > 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client > environment:user.name=root > 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] -
[jira] [Updated] (ZOOKEEPER-2539) Throwing nullpointerException when run the command "config -c" when client port is mentioned as separate and not like new style
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2539: -- Attachment: ConfigUtils.java.patch > Throwing nullpointerException when run the command "config -c" when client > port is mentioned as separate and not like new style > --- > > Key: ZOOKEEPER-2539 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2539 > Project: ZooKeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh >Priority: Minor > Attachments: ConfigUtils.java.patch > > > Throwing nullpointerException when run the command "config -c" when client > port is mentioned as separate and not like new style > 1. Configure the zookeeper to start in cluster mode like below- > clientPort=2181 > server.1=10.18.101.80:2888:3888 > server.2=10.18.219.50:2888:3888 > server.3=10.18.221.194:2888:3888 > and not like below:- > server.1=10.18.101.80:2888:3888:participant;2181 > server.2=10.18.219.50:2888:3888:participant;2181 > server.3=10.18.221.194:2888:3888:participant;2181 > 2. Start the cluster and one client using >zkCli.sh > 3. execute command "config -c" > It is throwing nullpointerException:- > root@BLR110865:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin# > ./zkCli.sh > Connecting to localhost:2181 > 2016-08-29 21:45:19,558 [myid:] - INFO [main:Environment@109] - Client > environment:zookeeper.version=3.5.1-alpha--1, built on 08/18/2016 08:20 GMT > 2016-08-29 21:45:19,561 [myid:] - INFO [main:Environment@109] - Client > environment:host.name=BLR110865 > 2016-08-29 21:45:19,562 [myid:] - INFO [main:Environment@109] - Client > environment:java.version=1.7.0_17 > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.vendor=Oracle Corporation > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.home=/usr/lib/jvm/oracle_jdk7/jre > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.class.path=/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../build/classes:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../build/lib/*.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/slf4j-log4j12-1.7.5.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/slf4j-api-1.7.5.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/servlet-api-2.5-20081211.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/netty-3.7.0.Final.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/log4j-1.2.16.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jline-2.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jetty-util-6.1.26.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jetty-6.1.26.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/javacc.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jackson-mapper-asl-1.9.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jackson-core-asl-1.9.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/commons-cli-1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/ant-eclipse-1.0-jvm1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../zookeeper-3.5.1-alpha.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../src/java/lib/ant-eclipse-1.0-jvm1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../conf: > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.library.path=/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.io.tmpdir=/tmp > 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client > environment:java.compiler= > 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client > environment:os.name=Linux > 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client > environment:os.arch=amd64 > 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client > environment:os.version=4.4.0-31-generic > 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client > environment:user.name=root > 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client > environment:user.home=/root > 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client
[jira] [Updated] (ZOOKEEPER-2537) When provide path for "dataDir" with heading space, it is taking correct path (by trucating space) for snapshot but zookeeper_server.pid is getting created in root (/
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2537: -- Attachment: zkServer.sh.patch > When provide path for "dataDir" with heading space, it is taking correct path > (by trucating space) for snapshot but zookeeper_server.pid is getting created > in root (/) folder > -- > > Key: ZOOKEEPER-2537 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2537 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh > Attachments: zkServer.sh.patch > > > Scenario 1 :- > When provide path for "dataDir" with heading space, it is taking correct path > (by trucating space) for snapshot but zookeeper_server.pid is getting created > in root (/) folder > Steps to reproduce:- > 1. Configure the dataDir > dataDir= /home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data > Here there is a space after dataDir= > 2. Start Zookeeper Server > 3. The snapshot is getting created at location mentioned above by truncating > the heading space but > zookeeper_server.pid is getting created at root (/) folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2536) When provide path for "dataDir" with trailing space, it is taking correct path (by trucating space) for snapshot but creating temporary file with some junk folder nam
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2536: -- Attachment: zkServer.sh.patch > When provide path for "dataDir" with trailing space, it is taking correct > path (by trucating space) for snapshot but creating temporary file with some > junk folder name for zookeeper_server.pid > > > Key: ZOOKEEPER-2536 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2536 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh > Attachments: zkServer.sh.patch > > > Scenario 1:- > When provide path for "dataDir" with trailing space, it is taking correct > path (by trucating space) for snapshot but creating temporary file with some > junk folder name for zookeeper_server.pid > Steps to reproduce:- > 1. Configure the dataDir > dataDir=/home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data > Here there is a space after /data > 2. Start Zookeeper Server > 3. The snapshot is getting created at location mentioned above by truncating > the trailing space but > one temp folder with junk name (like -> D29D4X~J) is getting created for > zookeeper_server.pid > Scenario 2:- > When configure the heading and trailing space in above mentioned scenario. > the temp folder is getting created in zookeeper/bin folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2541) We can't configure the "secureClientPort" in dynamicConfiguration and connect through client
Rakesh Kumar Singh created ZOOKEEPER-2541: - Summary: We can't configure the "secureClientPort" in dynamicConfiguration and connect through client Key: ZOOKEEPER-2541 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2541 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.1 Reporter: Rakesh Kumar Singh We can't configure the "secureClientPort" in dynamicConfiguration and connect through client Steps to reproduce:- 1. Configure the zookeeper in cluster mode with SSL mode 2. comment the clientport and secureClientport details from zoo.cfg file 3. Configure the secureClientport in dynamicConfiguration as below:- server.1=10.18.101.80:2888:3888:participant;2181 server.2=10.18.219.50:2888:3888:participant;2181 server.3=10.18.221.194:2888:3888:participant;2181 4. Start the cluster 5. Start one client using zkCli.sh and try to connect to any one of the cluster, it fails Client log:- BLR107042:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin # ./zkCli.sh /usr/bin/java Connecting to localhost:2181 2016-08-30 13:42:33,574 [myid:] - INFO [main:Environment@109] - Client environment:zookeeper.version=3.5.1-alpha--1, built on 08/18/2016 08:20 GMT 2016-08-30 13:42:33,578 [myid:] - INFO [main:Environment@109] - Client environment:host.name=BLR107042 2016-08-30 13:42:33,578 [myid:] - INFO [main:Environment@109] - Client environment:java.version=1.7.0_79 2016-08-30 13:42:33,581 [myid:] - INFO [main:Environment@109] - Client environment:java.vendor=Oracle Corporation 2016-08-30 13:42:33,581 [myid:] - INFO [main:Environment@109] - Client environment:java.home=/usr/java/jdk1.7.0_79/jre 2016-08-30 13:42:33,581 [myid:] - INFO [main:Environment@109] - Client environment:java.class.path=/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../build/classes:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../build/lib/*.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/slf4j-log4j12-1.7.5.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/slf4j-api-1.7.5.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/servlet-api-2.5-20081211.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/netty-3.7.0.Final.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/log4j-1.2.16.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jline-2.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jetty-util-6.1.26.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jetty-6.1.26.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/javacc.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jackson-mapper-asl-1.9.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jackson-core-asl-1.9.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/commons-cli-1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/ant-eclipse-1.0-jvm1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../zookeeper-3.5.1-alpha.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../src/java/lib/ant-eclipse-1.0-jvm1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../conf: 2016-08-30 13:42:33,582 [myid:] - INFO [main:Environment@109] - Client environment:java.library.path=/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib 2016-08-30 13:42:33,582 [myid:] - INFO [main:Environment@109] - Client environment:java.io.tmpdir=/tmp 2016-08-30 13:42:33,582 [myid:] - INFO [main:Environment@109] - Client environment:java.compiler= 2016-08-30 13:42:33,582 [myid:] - INFO [main:Environment@109] - Client environment:os.name=Linux 2016-08-30 13:42:33,582 [myid:] - INFO [main:Environment@109] - Client environment:os.arch=amd64 2016-08-30 13:42:33,583 [myid:] - INFO [main:Environment@109] - Client environment:os.version=3.0.76-0.11-default 2016-08-30 13:42:33,583 [myid:] - INFO [main:Environment@109] - Client environment:user.name=root 2016-08-30 13:42:33,583 [myid:] - INFO [main:Environment@109] - Client environment:user.home=/root 2016-08-30 13:42:33,583 [myid:] - INFO [main:Environment@109] - Client environment:user.dir=/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin 2016-08-30 13:42:33,583 [myid:] - INFO [main:Environment@109] - Client environment:os.memory.free=52MB 2016-08-30 13:42:33,586 [myid:] - INFO [main:Environment@109] - Client environment:os.memory.max=227MB 2016-08-30 13:42:33,587 [myid:] - INFO [main:Environment@109] - Client environment:os.memory.total=57MB 2016-08-30 13:42:33,591 [myid:] - INFO [main:ZooKeeper@716] - Initiating client
[jira] [Created] (ZOOKEEPER-2540) When start zookeeper server by configuring the server details in dynamic configuration with passing the client port, wrong log info is logged
Rakesh Kumar Singh created ZOOKEEPER-2540: - Summary: When start zookeeper server by configuring the server details in dynamic configuration with passing the client port, wrong log info is logged Key: ZOOKEEPER-2540 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2540 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.1 Reporter: Rakesh Kumar Singh Priority: Minor When start zookeeper server by configuring the server details in dynamic configuration with passing the client port, wrong log info is logged:- Configure the server details as below which contains client port as well and remove the client port from zoo.cfg (as it is duplicate) :- server.1=10.18.101.80:2888:3888:participant;2181 server.2=10.18.219.50:2888:3888:participant;2181 server.3=10.18.221.194:2888:3888:participant;2181 Start the cluster, we can see message as 2016-08-30 17:00:33,984 [myid:] - INFO [main:QuorumPeerConfig@306] - clientPort is not set which is not correct -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2539) Throwing nullpointerException when run the command "config -c" when client port is mentioned as separate and not like new style
Rakesh Kumar Singh created ZOOKEEPER-2539: - Summary: Throwing nullpointerException when run the command "config -c" when client port is mentioned as separate and not like new style Key: ZOOKEEPER-2539 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2539 Project: ZooKeeper Issue Type: Bug Components: java client Affects Versions: 3.5.1 Reporter: Rakesh Kumar Singh Priority: Minor Throwing nullpointerException when run the command "config -c" when client port is mentioned as separate and not like new style 1. Configure the zookeeper to start in cluster mode like below- clientPort=2181 server.1=10.18.101.80:2888:3888 server.2=10.18.219.50:2888:3888 server.3=10.18.221.194:2888:3888 and not like below:- server.1=10.18.101.80:2888:3888:participant;2181 server.2=10.18.219.50:2888:3888:participant;2181 server.3=10.18.221.194:2888:3888:participant;2181 2. Start the cluster and one client using >zkCli.sh 3. execute command "config -c" It is throwing nullpointerException:- root@BLR110865:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin# ./zkCli.sh Connecting to localhost:2181 2016-08-29 21:45:19,558 [myid:] - INFO [main:Environment@109] - Client environment:zookeeper.version=3.5.1-alpha--1, built on 08/18/2016 08:20 GMT 2016-08-29 21:45:19,561 [myid:] - INFO [main:Environment@109] - Client environment:host.name=BLR110865 2016-08-29 21:45:19,562 [myid:] - INFO [main:Environment@109] - Client environment:java.version=1.7.0_17 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client environment:java.vendor=Oracle Corporation 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client environment:java.home=/usr/lib/jvm/oracle_jdk7/jre 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client environment:java.class.path=/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../build/classes:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../build/lib/*.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/slf4j-log4j12-1.7.5.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/slf4j-api-1.7.5.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/servlet-api-2.5-20081211.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/netty-3.7.0.Final.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/log4j-1.2.16.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jline-2.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jetty-util-6.1.26.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jetty-6.1.26.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/javacc.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jackson-mapper-asl-1.9.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/jackson-core-asl-1.9.11.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/commons-cli-1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../lib/ant-eclipse-1.0-jvm1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../zookeeper-3.5.1-alpha.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../src/java/lib/ant-eclipse-1.0-jvm1.2.jar:/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin/../conf: 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client environment:java.library.path=/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client environment:java.io.tmpdir=/tmp 2016-08-29 21:45:19,564 [myid:] - INFO [main:Environment@109] - Client environment:java.compiler= 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client environment:os.name=Linux 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client environment:os.arch=amd64 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client environment:os.version=4.4.0-31-generic 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client environment:user.name=root 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client environment:user.home=/root 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client environment:user.dir=/home/Rakesh/Zookeeper/18_Aug/cluster/zookeeper-3.5.1-alpha/bin 2016-08-29 21:45:19,565 [myid:] - INFO [main:Environment@109] - Client environment:os.memory.free=114MB 2016-08-29 21:45:19,567 [myid:] - INFO [main:Environment@109] - Client environment:os.memory.max=227MB 2016-08-29 21:45:19,568 [myid:] - INFO [main:Environment@109] - Client environment:os.memory.total=119MB 2016-08-29
[jira] [Updated] (ZOOKEEPER-2536) When provide path for "dataDir" with trailing space, it is taking correct path (by trucating space) for snapshot but creating temporary file with some junk folder nam
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2536: -- Description: Scenario 1:- When provide path for "dataDir" with trailing space, it is taking correct path (by trucating space) for snapshot but creating temporary file with some junk folder name for zookeeper_server.pid Steps to reproduce:- 1. Configure the dataDir dataDir=/home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data Here there is a space after /data 2. Start Zookeeper Server 3. The snapshot is getting created at location mentioned above by truncating the trailing space but one temp folder with junk name (like -> D29D4X~J) is getting created for zookeeper_server.pid Scenario 2:- When configure the heading and trailing space in above mentioned scenario. the temp folder is getting created in zookeeper/bin folder was: When provide path for "dataDir" with trailing space, it is taking correct path (by trucating space) for snapshot but creating temporary file with some junk folder name for zookeeper_server.pid Steps to reproduce:- 1. Configure the dataDir dataDir=/home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data Here there is a space after /data 2. Start Zookeeper Server 3. The snapshot is getting created at location mentioned above by truncating the trailing space but one temp folder with junk name (like -> D29D4X~J) is getting created for zookeeper_server.pid > When provide path for "dataDir" with trailing space, it is taking correct > path (by trucating space) for snapshot but creating temporary file with some > junk folder name for zookeeper_server.pid > > > Key: ZOOKEEPER-2536 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2536 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh > > Scenario 1:- > When provide path for "dataDir" with trailing space, it is taking correct > path (by trucating space) for snapshot but creating temporary file with some > junk folder name for zookeeper_server.pid > Steps to reproduce:- > 1. Configure the dataDir > dataDir=/home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data > Here there is a space after /data > 2. Start Zookeeper Server > 3. The snapshot is getting created at location mentioned above by truncating > the trailing space but > one temp folder with junk name (like -> D29D4X~J) is getting created for > zookeeper_server.pid > Scenario 2:- > When configure the heading and trailing space in above mentioned scenario. > the temp folder is getting created in zookeeper/bin folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2537) When provide path for "dataDir" with heading space, it is taking correct path (by trucating space) for snapshot but zookeeper_server.pid is getting created in root (/
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2537: -- Description: Scenario 1 :- When provide path for "dataDir" with heading space, it is taking correct path (by trucating space) for snapshot but zookeeper_server.pid is getting created in root (/) folder Steps to reproduce:- 1. Configure the dataDir dataDir= /home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data Here there is a space after dataDir= 2. Start Zookeeper Server 3. The snapshot is getting created at location mentioned above by truncating the heading space but zookeeper_server.pid is getting created at root (/) folder was: When provide path for "dataDir" with heading space, it is taking correct path (by trucating space) for snapshot but zookeeper_server.pid is getting created in root (/) folder Steps to reproduce:- 1. Configure the dataDir dataDir= /home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data Here there is a space after dataDir= 2. Start Zookeeper Server 3. The snapshot is getting created at location mentioned above by truncating the heading space but zookeeper_server.pid is getting created at root (/) folder > When provide path for "dataDir" with heading space, it is taking correct path > (by trucating space) for snapshot but zookeeper_server.pid is getting created > in root (/) folder > -- > > Key: ZOOKEEPER-2537 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2537 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh > > Scenario 1 :- > When provide path for "dataDir" with heading space, it is taking correct path > (by trucating space) for snapshot but zookeeper_server.pid is getting created > in root (/) folder > Steps to reproduce:- > 1. Configure the dataDir > dataDir= /home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data > Here there is a space after dataDir= > 2. Start Zookeeper Server > 3. The snapshot is getting created at location mentioned above by truncating > the heading space but > zookeeper_server.pid is getting created at root (/) folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2537) When provide path for "dataDir" with heading space, it is taking correct path (by trucating space) for snapshot but zookeeper_server.pid is getting created in root (/
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2537: -- Priority: Major (was: Minor) > When provide path for "dataDir" with heading space, it is taking correct path > (by trucating space) for snapshot but zookeeper_server.pid is getting created > in root (/) folder > -- > > Key: ZOOKEEPER-2537 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2537 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh > > When provide path for "dataDir" with heading space, it is taking correct path > (by trucating space) for snapshot but zookeeper_server.pid is getting created > in root (/) folder > Steps to reproduce:- > 1. Configure the dataDir > dataDir= /home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data > Here there is a space after dataDir= > 2. Start Zookeeper Server > 3. The snapshot is getting created at location mentioned above by truncating > the heading space but > zookeeper_server.pid is getting created at root (/) folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2537) When provide path for "dataDir" with heading space, it is taking correct path (by trucating space) for snapshot but zookeeper_server.pid is getting created in root (/
Rakesh Kumar Singh created ZOOKEEPER-2537: - Summary: When provide path for "dataDir" with heading space, it is taking correct path (by trucating space) for snapshot but zookeeper_server.pid is getting created in root (/) folder Key: ZOOKEEPER-2537 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2537 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.2, 3.5.1 Reporter: Rakesh Kumar Singh Priority: Minor When provide path for "dataDir" with heading space, it is taking correct path (by trucating space) for snapshot but zookeeper_server.pid is getting created in root (/) folder Steps to reproduce:- 1. Configure the dataDir dataDir= /home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data Here there is a space after dataDir= 2. Start Zookeeper Server 3. The snapshot is getting created at location mentioned above by truncating the heading space but zookeeper_server.pid is getting created at root (/) folder -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2536) When provide path for "dataDir" with trailing space, it is taking correct path (by trucating space) for snapshot but creating temporary file with some junk folder nam
Rakesh Kumar Singh created ZOOKEEPER-2536: - Summary: When provide path for "dataDir" with trailing space, it is taking correct path (by trucating space) for snapshot but creating temporary file with some junk folder name for zookeeper_server.pid Key: ZOOKEEPER-2536 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2536 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.2, 3.5.1 Reporter: Rakesh Kumar Singh When provide path for "dataDir" with trailing space, it is taking correct path (by trucating space) for snapshot but creating temporary file with some junk folder name for zookeeper_server.pid Steps to reproduce:- 1. Configure the dataDir dataDir=/home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data Here there is a space after /data 2. Start Zookeeper Server 3. The snapshot is getting created at location mentioned above by truncating the trailing space but one temp folder with junk name (like -> D29D4X~J) is getting created for zookeeper_server.pid -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2535) zookeeper_server's pid should be created once server is started completely and not before, problem with current approach
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2535: -- Description: zookeeper_server's pid should be created once server is started completely and not before, problem with current approach :- Scenario:- 1. Configure below in zoo.cfg dataDir=/home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data 2. Start zookeeper server 3. Change the dataDir to suppose dataDir=/home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data1 4. Again start zookeeper without stopping zookeeper. Though it will fail to start the server as port is already bind, it will create "zookeeper_server.pid" file with different PID inside and "version-2" folder Now again revertback the dataDir path and stop the server, the new created folder and file at step 4 remained was: zookeeper_server's pid should be created once server is started and not before, problem with current approach :- Scenario:- 1. Configure below in zoo.cfg dataDir=/home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data 2. Start zookeeper server 3. Change the dataDir to suppose dataDir=/home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data1 4. Again start zookeeper without stopping zookeeper. Though it will fail to start the server as port is already bind, it will create "zookeeper_server.pid" file with different PID inside and "version-2" folder Now again revertback the dataDir path and stop the server, the new created folder and file at step 4 remained > zookeeper_server's pid should be created once server is started completely > and not before, problem with current approach > > > Key: ZOOKEEPER-2535 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2535 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh > > zookeeper_server's pid should be created once server is started completely > and not before, problem with current approach :- > Scenario:- > 1. Configure below in zoo.cfg > dataDir=/home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data > 2. Start zookeeper server > 3. Change the dataDir to suppose > dataDir=/home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data1 > 4. Again start zookeeper without stopping zookeeper. > Though it will fail to start the server as port is already bind, it will > create "zookeeper_server.pid" file with different PID inside and "version-2" > folder > Now again revertback the dataDir path and stop the server, the new created > folder and file at step 4 remained -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2535) zookeeper_server's pid should be created once server is started completely and not before, problem with current approach
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2535: -- Summary: zookeeper_server's pid should be created once server is started completely and not before, problem with current approach (was: zookeeper_server's pid should be created once server is started and not before, problem with current approach) > zookeeper_server's pid should be created once server is started completely > and not before, problem with current approach > > > Key: ZOOKEEPER-2535 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2535 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.5.1 >Reporter: Rakesh Kumar Singh > > zookeeper_server's pid should be created once server is started and not > before, problem with current approach :- > Scenario:- > 1. Configure below in zoo.cfg > dataDir=/home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data > 2. Start zookeeper server > 3. Change the dataDir to suppose > dataDir=/home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data1 > 4. Again start zookeeper without stopping zookeeper. > Though it will fail to start the server as port is already bind, it will > create "zookeeper_server.pid" file with different PID inside and "version-2" > folder > Now again revertback the dataDir path and stop the server, the new created > folder and file at step 4 remained -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2535) zookeeper_server's pid should be created once server is started and not before, problem with current approach
Rakesh Kumar Singh created ZOOKEEPER-2535: - Summary: zookeeper_server's pid should be created once server is started and not before, problem with current approach Key: ZOOKEEPER-2535 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2535 Project: ZooKeeper Issue Type: Bug Components: server Affects Versions: 3.5.1 Reporter: Rakesh Kumar Singh zookeeper_server's pid should be created once server is started and not before, problem with current approach :- Scenario:- 1. Configure below in zoo.cfg dataDir=/home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data 2. Start zookeeper server 3. Change the dataDir to suppose dataDir=/home/Rakesh/Zookeeper/18_Aug/zookeeper-3.5.1-alpha/data1 4. Again start zookeeper without stopping zookeeper. Though it will fail to start the server as port is already bind, it will create "zookeeper_server.pid" file with different PID inside and "version-2" folder Now again revertback the dataDir path and stop the server, the new created folder and file at step 4 remained -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2534) Configuration for IP address (zookeeper.server.ip=) should be introduced and zookeeper server should bind to that particular IP only not to all IPs of the system
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh Kumar Singh updated ZOOKEEPER-2534: -- Component/s: security > Configuration for IP address (zookeeper.server.ip=) should be introduced and > zookeeper server should bind to that particular IP only not to all IPs of the > system > - > > Key: ZOOKEEPER-2534 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2534 > Project: ZooKeeper > Issue Type: Bug > Components: security >Affects Versions: 3.5.1, 3.5.2 >Reporter: Rakesh Kumar Singh > > Configuration for IP address (zookeeper.server.ip=) should be introduced and > zookeeper server should bind to that particular IP only not to all IPs of the > system. As of now zookeeper is binding to 0.0.0.0 (all IPs - 127.0.0.1, IPv4, > IPv6) of the system. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
