ZooKeeper_branch34_jdk7 - Build # 1274 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_jdk7/1274/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 186306 lines...]
[junit] 2016-10-27 02:47:52,037 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2016-10-27 02:47:52,038 [myid:] - INFO  [main:ZooKeeperServer@497] 
- shutting down
[junit] 2016-10-27 02:47:52,038 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-10-27 02:47:52,038 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2016-10-27 02:47:52,038 [myid:] - INFO  
[main:PrepRequestProcessor@765] - Shutting down
[junit] 2016-10-27 02:47:52,039 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2016-10-27 02:47:52,039 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2016-10-27 02:47:52,040 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2016-10-27 02:47:52,040 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2016-10-27 02:47:52,041 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-10-27 02:47:52,042 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-10-27 02:47:52,044 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2016-10-27 02:47:52,044 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2016-10-27 02:47:52,045 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2016-10-27 02:47:52,045 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2016-10-27 02:47:52,046 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/build/test/tmp/test8634714111554568468.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/build/test/tmp/test8634714111554568468.junit.dir/version-2
[junit] 2016-10-27 02:47:52,051 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-10-27 02:47:52,051 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-10-27 02:47:52,053 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:56027
[junit] 2016-10-27 02:47:52,053 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:56027
[junit] 2016-10-27 02:47:52,054 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2016-10-27 02:47:52,055 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:56027 (no session established for client)
[junit] 2016-10-27 02:47:52,055 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-10-27 02:47:52,057 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2016-10-27 02:47:52,057 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2016-10-27 02:47:52,058 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-10-27 02:47:52,058 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-10-27 02:47:52,059 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 32604
[junit] 2016-10-27 02:47:52,059 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2016-10-27 02:47:52,059 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2016-10-27 02:47:52,059 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2016-10-27 02:47:52,091 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x15804095a1b closed
[junit] 2016-10-27 02:47:52,091 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2016-10-27 02:47:52,091 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2016-10-27 

[jira] [Commented] (ZOOKEEPER-1394) ClassNotFoundException on shutdown of client

[wu wen (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15610385#comment-15610385
 ] 

wu wen commented on ZOOKEEPER-1394:
---

also in  jboss

jBPMClusteredScheduler_$_brmsperf02.mw.lab.eng.bos.redhat.com1425567199094 
shutdown complete.
09:58:29,651 INFO  [org.jbpm.executor.impl.ExecutorImpl] (MSC service thread 
1-6)  > Destroying Executor !!!
09:58:29,733 ERROR [org.apache.zookeeper.ClientCnxn] (MSC service thread 
1-6-SendThread(brmsperf03:2181)) from MSC service thread 
1-6-SendThread(brmsperf03:2181): java.lang.NoClassDefFoundError: 
org/apache/zookeeper/server/ZooTrace
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1223) 
[zookeeper-3.3.4.jar:3.3.3-1203054]
Caused by: java.lang.ClassNotFoundException: 
org.apache.zookeeper.server.ZooTrace from [Module 
"deployment.business-central.war:main" from Service Module Loader]
at 
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) 
[jboss-modules.jar:1.3.6.Final-redhat-1]
at 
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459)
 [jboss-modules.jar:1.3.6.Final-redhat-1]
at 
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408)
 [jboss-modules.jar:1.3.6.Final-redhat-1]
at 
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389)
 [jboss-modules.jar:1.3.6.Final-redhat-1]
at 
org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134)
 [jboss-modules.jar:1.3.6.Final-redhat-1]
... 1 more


> ClassNotFoundException on shutdown of client
> 
>
> Key: ZOOKEEPER-1394
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1394
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.2
> Environment: OS X 10.7 java version "1.6.0_29"
>Reporter: Herman Meerlo
>Assignee: wu wen
>Priority: Minor
> Attachments: ZOOKEEPER-1394.patch
>
>
> When close() is called on the ZooKeeper instance from a ContextListener 
> (contextDestroyed) there is no way to synchronize with the fact that the 
> EventThread and SendThread have actually finished their work. The problem 
> lies in the SendThread which makes a call to ZooTrace when it exits, but that 
> class has not been loaded yet. Because the ContextListener could not 
> synchronize with the death of the threads the classloader has already 
> disappeared, resulting in a ClassNotFoundException.
> My personal opinion is that the close() method should probably wait until the 
> event and send thread have actually died.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-1394) ClassNotFoundException on shutdown of client

[wu wen (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15610360#comment-15610360
 ] 

wu wen commented on ZOOKEEPER-1394:
---

Look here 
http://zookeeper-user.578899.n2.nabble.com/java-lang-NoClassDefFoundError-org-apache-zookeeper-server-ZooTrace-td7578739.html

when using Zookeeper client API in tomcat and shut down tomcat.


> ClassNotFoundException on shutdown of client
> 
>
> Key: ZOOKEEPER-1394
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1394
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.2
> Environment: OS X 10.7 java version "1.6.0_29"
>Reporter: Herman Meerlo
>Assignee: wu wen
>Priority: Minor
> Attachments: ZOOKEEPER-1394.patch
>
>
> When close() is called on the ZooKeeper instance from a ContextListener 
> (contextDestroyed) there is no way to synchronize with the fact that the 
> EventThread and SendThread have actually finished their work. The problem 
> lies in the SendThread which makes a call to ZooTrace when it exits, but that 
> class has not been loaded yet. Because the ContextListener could not 
> synchronize with the death of the threads the classloader has already 
> disappeared, resulting in a ClassNotFoundException.
> My personal opinion is that the close() method should probably wait until the 
> event and send thread have actually died.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper_branch34 - Build # 1701 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34/1701/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 183801 lines...]
[junit] 2016-10-27 00:13:41,574 [myid:] - INFO  [main:ZooKeeperServer@497] 
- shutting down
[junit] 2016-10-27 00:13:41,574 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-10-27 00:13:41,574 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2016-10-27 00:13:41,575 [myid:] - INFO  
[main:PrepRequestProcessor@765] - Shutting down
[junit] 2016-10-27 00:13:41,575 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2016-10-27 00:13:41,575 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2016-10-27 00:13:41,575 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2016-10-27 00:13:41,576 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2016-10-27 00:13:41,577 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-10-27 00:13:41,578 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-10-27 00:13:41,579 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2016-10-27 00:13:41,580 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2016-10-27 00:13:41,580 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2016-10-27 00:13:41,581 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2016-10-27 00:13:41,581 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/test/tmp/test6407426713484833023.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/test/tmp/test6407426713484833023.junit.dir/version-2
[junit] 2016-10-27 00:13:41,586 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-10-27 00:13:41,587 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-10-27 00:13:41,587 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:57059
[junit] 2016-10-27 00:13:41,587 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:57059
[junit] 2016-10-27 00:13:41,588 [myid:] - INFO  
[Thread-5:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2016-10-27 00:13:41,589 [myid:] - INFO  
[Thread-5:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:57059 (no session established for client)
[junit] 2016-10-27 00:13:41,589 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-10-27 00:13:41,591 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2016-10-27 00:13:41,591 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2016-10-27 00:13:41,591 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-10-27 00:13:41,592 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-10-27 00:13:41,592 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 31168
[junit] 2016-10-27 00:13:41,592 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2016-10-27 00:13:41,593 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2016-10-27 00:13:41,593 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2016-10-27 00:13:41,653 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x158037c3496 closed
[junit] 2016-10-27 00:13:41,653 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2016-10-27 00:13:41,653 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x158037c3496
[junit] 2016-10-27 00:13:41,653 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2016-10-27 00:13:41,654 [myid:] - 

[jira] [Commented] (ZOOKEEPER-2556) peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime

[Michael Han (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15610049#comment-15610049
 ] 

Michael Han commented on ZOOKEEPER-2556:


[~shralex] I don't have write access :-) Also one suggestion - given that we 
have git merge script integrated in the repo maybe [~rakeshsingh] should create 
a PR for ZOOKEEPER-2556 and then a committer can merge the PR. The benefit of 
committing through PR is the contributors get their credit in commit history, 
i.e. see 
[this|https://github.com/apache/zookeeper/commit/f6349d16fcd5f04b560095417fd2a1813ac3e855].
 

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

ZooKeeper_branch34_jdk8 - Build # 750 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_jdk8/750/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 191767 lines...]
[junit] 2016-10-26 23:22:47,419 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2016-10-26 23:22:47,419 [myid:] - INFO  [main:ZooKeeperServer@497] 
- shutting down
[junit] 2016-10-26 23:22:47,419 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-10-26 23:22:47,420 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2016-10-26 23:22:47,420 [myid:] - INFO  
[main:PrepRequestProcessor@765] - Shutting down
[junit] 2016-10-26 23:22:47,420 [myid:] - INFO  
[main:SyncRequestProcessor@208] - Shutting down
[junit] 2016-10-26 23:22:47,420 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2016-10-26 23:22:47,420 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited!
[junit] 2016-10-26 23:22:47,420 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2016-10-26 23:22:47,421 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-10-26 23:22:47,421 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-10-26 23:22:47,423 [myid:] - INFO  [main:ClientBase@445] - 
STARTING server
[junit] 2016-10-26 23:22:47,423 [myid:] - INFO  [main:ClientBase@366] - 
CREATING server instance 127.0.0.1:11221
[junit] 2016-10-26 23:22:47,423 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2016-10-26 23:22:47,424 [myid:] - INFO  [main:ClientBase@341] - 
STARTING server instance 127.0.0.1:11221
[junit] 2016-10-26 23:22:47,424 [myid:] - INFO  [main:ZooKeeperServer@173] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/build/test/tmp/test2188754690755145324.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/build/test/tmp/test2188754690755145324.junit.dir/version-2
[junit] 2016-10-26 23:22:47,427 [myid:] - ERROR [main:ZooKeeperServer@472] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-10-26 23:22:47,427 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-10-26 23:22:47,427 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:57221
[junit] 2016-10-26 23:22:47,428 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:57221
[junit] 2016-10-26 23:22:47,428 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2016-10-26 23:22:47,429 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:57221 (no session established for client)
[junit] 2016-10-26 23:22:47,429 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-10-26 23:22:47,430 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2016-10-26 23:22:47,431 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2016-10-26 23:22:47,431 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-10-26 23:22:47,431 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-10-26 23:22:47,431 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 33587
[junit] 2016-10-26 23:22:47,431 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2016-10-26 23:22:47,432 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2016-10-26 23:22:47,432 [myid:] - INFO  [main:ClientBase@522] - 
tearDown starting
[junit] 2016-10-26 23:22:47,498 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x158034d983a closed
[junit] 2016-10-26 23:22:47,498 [myid:] - INFO  [main:ClientBase@492] - 
STOPPING server
[junit] 2016-10-26 23:22:47,498 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x158034d983a
[junit] 2016-10-26 23:22:47,499 

[jira] [Commented] (ZOOKEEPER-2556) peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime

[Alexander Shraer (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15609825#comment-15609825
 ] 

Alexander Shraer commented on ZOOKEEPER-2556:
-

+1

[~hanm], [~breed], would you guys be able to commit this ? I still need to 
learn the new git procedure :)

> 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, 
> 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-2597) Add script to merge PR from Apache git repo to Github

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15609276#comment-15609276
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2597:
---

Github user edwardoliveira commented on the issue:

https://github.com/apache/zookeeper/pull/85
  
Thanks @hanm ! :smiley: 


> Add script to merge PR from Apache git repo to Github
> -
>
> Key: ZOOKEEPER-2597
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2597
> Project: ZooKeeper
>  Issue Type: Improvement
>Reporter: Edward Ribeiro
>Assignee: Edward Ribeiro
>Priority: Minor
> Attachments: ZOOKEEPER-2597.patch
>
>
> A port of kafka-merge-pr.py to workon on ZooKeeper repo.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] zookeeper issue #85: ZOOKEEPER-2597: Add script to merge PR from Apache git ...

[edwardoliveira]

Github user edwardoliveira commented on the issue:

https://github.com/apache/zookeeper/pull/85
  
Thanks @hanm ! :smiley: 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [VOTE] move Apache Zookeeper to git

[Edward Ribeiro]

AFAIK, yes. I say, if you mean to run unit tests and other CI tasks on PR.

PS: I have just created a simple script HowTo at
https://cwiki.apache.org/confluence/display/ZOOKEEPER/Merging+Github+Pull+Requests
and linked from https://cwiki.apache.org/confluence/display/ZOOKEEPER/Index

On Wed, Oct 26, 2016 at 3:59 PM, Flavio Junqueira  wrote:

> What about QA, are we still missing a github pre-commit queue?
>
> -Flavio
>
> > On 26 Oct 2016, at 18:53, Michael Han  wrote:
> >
> > The comment bridging should be fixed now - see INFRA-12752 for more
> > details.
> >
> > On Wed, Oct 26, 2016 at 10:03 AM, Michael Han  wrote:
> >
>  The git PR *review* comments for ZOOKEEPER-2597 didn't show up on
> JIRA.
> >>
> >> The bridge was working the day Infra made the change - see the previous
> >> comments made by git bot on ZOOKEEPER-761. Now it seems stop working. I
> am
> >> reopening INFRA-12752 and building a case.
> >>
> >> On Wed, Oct 26, 2016 at 9:45 AM, Edward Ribeiro <
> edward.ribe...@gmail.com>
> >> wrote:
> >>
> >>> Dear community,
> >>>
> >>> The zk-merger-pr.py script has been merged into master (thanks a LOT
> Ben
> >>> Reed for reviewing/discussing/testing and commiting):
> >>> https://issues.apache.org/jira/browse/ZOOKEEPER-2597
> >>>
> >>> As stated in the issue and on GH, this tool is a modified version of
> >>> similar tools from Kafka, that is a copy of a Spark's one. It has some
> >>> rough edges so we will certainly benefit from further enhancements and
> >>> fixes. I changed the smallest possible pieces of code, just to make it
> >>> work
> >>> on a ZK repo so the credits go to the original authors.
> >>>
> >>> Some notes:
> >>>
> >>> 1. The git PR *review* comments for ZOOKEEPER-2597 didn't show up on
> JIRA.
> >>> Only the opening and closing of the issue. Can we double check this as
> >>> INFRA-12752 is closed, Michael Han?
> >>>
> >>> 2. I scribbled a draft on how use the tool at
> >>> https://docs.google.com/document/d/1i00ZXjrW2fu17vr_h7F1bUrq
> >>> Xg3urw4Hm7KirQDpPIU/edit
> >>> (still very crude, but feel free to improve it). I would like to move
> >>> this
> >>> text to https://cwiki.apache.org/confluence/display/ZOOKEEPER/Index
> but
> >>> looks like I don't have permission to create a page there yet. Any
> help?
> >>>
> >>> Best regards,
> >>> Eddie
> >>>
> >>> On Sat, Oct 22, 2016 at 7:08 PM, Michael Han 
> wrote:
> >>>
>  FYI infra did some work in INFRA-12752 and the git PR comments can be
>  pushed to Apache JIRA.
> 
>  On Sat, Oct 8, 2016 at 8:01 AM, Flavio Junqueira 
> >>> wrote:
> 
> > This is not supported at the moment if nothing has changed:
> >
> > https://issues.apache.org/jira/browse/INFRA-11000 <
> > https://issues.apache.org/jira/browse/INFRA-11000>
> >
> > -Flavio
> >
> >> On 08 Oct 2016, at 00:54, Benjamin Reed  wrote:
> >>
> >> it doesn't look like we need to setup keys. this seems to work for
> >>> me:
> >>
> >> https://git-wip-us.apache.org/#committers-getting-started
> >>
> >> it does seem strange that we aren't using public keys and that i'm
> > sticking
> >> a password in .netrc :P i'm wondering if other projects were able to
>  get
> >> this going over ssh.
> >>
> >> i'll take a whack at cleaning up the svn and subversion references.
> >>
> >> ben
> >>
> >> On Fri, Oct 7, 2016 at 12:59 PM, Camille Fournier <
> >>> cami...@apache.org>
> >> wrote:
> >>
> >>> Hey folks,
> >>>
> >>> So I'm trying to get in a patch but this has not been updated to
> >>> tell
> >>> committers how to actually get the git keys set up:
> >>> https://cwiki.apache.org/confluence/display/ZOOKEEPER/
> > Committing+changes
> >>>
> >>> Can someone float me a link that says how to do this?
> >>>
> >>> Also a bunch of our documentation still discusses SVN and not git,
>  which
> >>> means we are not done with this migration. If you were pushing for
>  this
> >>> change can you please do some due diligence on the wikis and
> >>> correct
>  the
> >>> stuff that refers to SVN?
> >>>
> >>> Thanks,
> >>> C
> >>>
> >>> On Wed, Oct 5, 2016 at 1:02 PM, Edward Ribeiro <
> > edward.ribe...@gmail.com>
> >>> wrote:
> >>>
>  Excuse me guys!
> 
>  I've written on Macbook Pro. No idea why GMail messed it up. I was
>  only
>  able to see the strange characters when I pasted on a gist text
> >>> area.
> > The
>  previous message is below, but if anyone is still having trouble
> >>> (I
> > tried
>  to remove the weird character), I left a copy at:
>  https://gist.github.com/eribeiro/da2a6a6c9a508610d52d0755fae8352d
> 
>  "Hi,
> 
>  The patch attached on ZOOKEEPER-2597 is a straightforward

[jira] [Commented] (ZOOKEEPER-2597) Add script to merge PR from Apache git repo to Github

[Edward Ribeiro (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15609220#comment-15609220
 ] 

Edward Ribeiro commented on ZOOKEEPER-2597:
---

Thanks Michael! :)



On Wed, Oct 26, 2016 at 3:51 PM, ASF GitHub Bot (JIRA) 



> Add script to merge PR from Apache git repo to Github
> -
>
> Key: ZOOKEEPER-2597
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2597
> Project: ZooKeeper
>  Issue Type: Improvement
>Reporter: Edward Ribeiro
>Assignee: Edward Ribeiro
>Priority: Minor
> Attachments: ZOOKEEPER-2597.patch
>
>
> A port of kafka-merge-pr.py to workon on ZooKeeper repo.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] move Apache Zookeeper to git

[Flavio Junqueira]

What about QA, are we still missing a github pre-commit queue?

-Flavio

> On 26 Oct 2016, at 18:53, Michael Han  wrote:
> 
> The comment bridging should be fixed now - see INFRA-12752 for more
> details.
> 
> On Wed, Oct 26, 2016 at 10:03 AM, Michael Han  wrote:
> 
 The git PR *review* comments for ZOOKEEPER-2597 didn't show up on JIRA.
>> 
>> The bridge was working the day Infra made the change - see the previous
>> comments made by git bot on ZOOKEEPER-761. Now it seems stop working. I am
>> reopening INFRA-12752 and building a case.
>> 
>> On Wed, Oct 26, 2016 at 9:45 AM, Edward Ribeiro 
>> wrote:
>> 
>>> Dear community,
>>> 
>>> The zk-merger-pr.py script has been merged into master (thanks a LOT Ben
>>> Reed for reviewing/discussing/testing and commiting):
>>> https://issues.apache.org/jira/browse/ZOOKEEPER-2597
>>> 
>>> As stated in the issue and on GH, this tool is a modified version of
>>> similar tools from Kafka, that is a copy of a Spark's one. It has some
>>> rough edges so we will certainly benefit from further enhancements and
>>> fixes. I changed the smallest possible pieces of code, just to make it
>>> work
>>> on a ZK repo so the credits go to the original authors.
>>> 
>>> Some notes:
>>> 
>>> 1. The git PR *review* comments for ZOOKEEPER-2597 didn't show up on JIRA.
>>> Only the opening and closing of the issue. Can we double check this as
>>> INFRA-12752 is closed, Michael Han?
>>> 
>>> 2. I scribbled a draft on how use the tool at
>>> https://docs.google.com/document/d/1i00ZXjrW2fu17vr_h7F1bUrq
>>> Xg3urw4Hm7KirQDpPIU/edit
>>> (still very crude, but feel free to improve it). I would like to move
>>> this
>>> text to https://cwiki.apache.org/confluence/display/ZOOKEEPER/Index but
>>> looks like I don't have permission to create a page there yet. Any help?
>>> 
>>> Best regards,
>>> Eddie
>>> 
>>> On Sat, Oct 22, 2016 at 7:08 PM, Michael Han  wrote:
>>> 
 FYI infra did some work in INFRA-12752 and the git PR comments can be
 pushed to Apache JIRA.
 
 On Sat, Oct 8, 2016 at 8:01 AM, Flavio Junqueira 
>>> wrote:
 
> This is not supported at the moment if nothing has changed:
> 
> https://issues.apache.org/jira/browse/INFRA-11000 <
> https://issues.apache.org/jira/browse/INFRA-11000>
> 
> -Flavio
> 
>> On 08 Oct 2016, at 00:54, Benjamin Reed  wrote:
>> 
>> it doesn't look like we need to setup keys. this seems to work for
>>> me:
>> 
>> https://git-wip-us.apache.org/#committers-getting-started
>> 
>> it does seem strange that we aren't using public keys and that i'm
> sticking
>> a password in .netrc :P i'm wondering if other projects were able to
 get
>> this going over ssh.
>> 
>> i'll take a whack at cleaning up the svn and subversion references.
>> 
>> ben
>> 
>> On Fri, Oct 7, 2016 at 12:59 PM, Camille Fournier <
>>> cami...@apache.org>
>> wrote:
>> 
>>> Hey folks,
>>> 
>>> So I'm trying to get in a patch but this has not been updated to
>>> tell
>>> committers how to actually get the git keys set up:
>>> https://cwiki.apache.org/confluence/display/ZOOKEEPER/
> Committing+changes
>>> 
>>> Can someone float me a link that says how to do this?
>>> 
>>> Also a bunch of our documentation still discusses SVN and not git,
 which
>>> means we are not done with this migration. If you were pushing for
 this
>>> change can you please do some due diligence on the wikis and
>>> correct
 the
>>> stuff that refers to SVN?
>>> 
>>> Thanks,
>>> C
>>> 
>>> On Wed, Oct 5, 2016 at 1:02 PM, Edward Ribeiro <
> edward.ribe...@gmail.com>
>>> wrote:
>>> 
 Excuse me guys!
 
 I've written on Macbook Pro. No idea why GMail messed it up. I was
 only
 able to see the strange characters when I pasted on a gist text
>>> area.
> The
 previous message is below, but if anyone is still having trouble
>>> (I
> tried
 to remove the weird character), I left a copy at:
 https://gist.github.com/eribeiro/da2a6a6c9a508610d52d0755fae8352d
 
 "Hi,
 
 The patch attached on ZOOKEEPER-2597 is a straightforward
>>> adaptation
 of
 Kafka's one. It takes care of merging Github PR into Apache git
>>> repo
> and
>>> a
 subsequent closing of the PR on the GH side, among other things
>>> (rewriting
 of commit messages, etc). The current status is: the script needs
>>> to
 be
 reviewed/validated by a committer. It has been some time since I
> uploaded
 the patch, so I gonna do another pass through it in the meantime.
 
 There are some workflow issues beyond the scope of ZOOKEEPER-2597
 that
>>> need
 to be 

[jira] [Commented] (ZOOKEEPER-761) Remove *synchronous* calls from the *single-threaded* C clieant API, since they are documented not to work

[Flavio Junqueira (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15609180#comment-15609180
 ] 

Flavio Junqueira commented on ZOOKEEPER-761:


Hmm, the github stuff is also not running QA, right?

> Remove *synchronous* calls from the *single-threaded* C clieant API, since 
> they are documented not to work
> --
>
> Key: ZOOKEEPER-761
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-761
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: c client
>Affects Versions: 3.1.1, 3.2.2
> Environment: RHEL 4u8 (Linux).  The issue is not OS-specific though.
>Reporter: Jozef Hatala
>Assignee: Benjamin Reed
>Priority: Minor
> Fix For: 3.5.3, 3.6.0
>
> Attachments: fix-sync-apis-in-st-adaptor.patch, 
> fix-sync-apis-in-st-adaptor.v2.patch
>
>
> Since the synchronous calls are 
> [known|http://hadoop.apache.org/zookeeper/docs/current/zookeeperProgrammers.html#Using+the+C+Client]
>  to be unimplemented in the single threaded version of the client library 
> libzookeeper_st.so, I believe that it would be helpful towards users of the 
> library if that information was also obvious from the header file.
> Anecdotally more than one of us here made the mistake of starting by using 
> the synchronous calls with the single-threaded library, and we found 
> ourselves debugging it.  An early warning would have been greatly appreciated.
> 1. Could you please add warnings to the doxygen blocks of all synchronous 
> calls saying that they are not available in the single-threaded API.  This 
> cannot be safely done with {{#ifdef THREADED}}, obviously, because the same 
> header file is included whichever client library implementation one is 
> compiling for.
> 2. Could you please bracket the implementation of all synchronous calls in 
> zookeeper.c with {{#ifdef THREADED}} and {{#endif}}, so that those symbols 
> are not present in libzookeeper_st.so?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] move Apache Zookeeper to git

[Michael Han]

The comment bridging should be fixed now - see INFRA-12752 for more
details.

On Wed, Oct 26, 2016 at 10:03 AM, Michael Han  wrote:

> >> The git PR *review* comments for ZOOKEEPER-2597 didn't show up on JIRA.
>
> The bridge was working the day Infra made the change - see the previous
> comments made by git bot on ZOOKEEPER-761. Now it seems stop working. I am
> reopening INFRA-12752 and building a case.
>
> On Wed, Oct 26, 2016 at 9:45 AM, Edward Ribeiro 
> wrote:
>
>> Dear community,
>>
>> The zk-merger-pr.py script has been merged into master (thanks a LOT Ben
>> Reed for reviewing/discussing/testing and commiting):
>> https://issues.apache.org/jira/browse/ZOOKEEPER-2597
>>
>> As stated in the issue and on GH, this tool is a modified version of
>> similar tools from Kafka, that is a copy of a Spark's one. It has some
>> rough edges so we will certainly benefit from further enhancements and
>> fixes. I changed the smallest possible pieces of code, just to make it
>> work
>> on a ZK repo so the credits go to the original authors.
>>
>> Some notes:
>>
>> 1. The git PR *review* comments for ZOOKEEPER-2597 didn't show up on JIRA.
>> Only the opening and closing of the issue. Can we double check this as
>> INFRA-12752 is closed, Michael Han?
>>
>> 2. I scribbled a draft on how use the tool at
>> https://docs.google.com/document/d/1i00ZXjrW2fu17vr_h7F1bUrq
>> Xg3urw4Hm7KirQDpPIU/edit
>>  (still very crude, but feel free to improve it). I would like to move
>> this
>> text to https://cwiki.apache.org/confluence/display/ZOOKEEPER/Index but
>> looks like I don't have permission to create a page there yet. Any help?
>>
>> Best regards,
>> Eddie
>>
>> On Sat, Oct 22, 2016 at 7:08 PM, Michael Han  wrote:
>>
>> > FYI infra did some work in INFRA-12752 and the git PR comments can be
>> > pushed to Apache JIRA.
>> >
>> > On Sat, Oct 8, 2016 at 8:01 AM, Flavio Junqueira 
>> wrote:
>> >
>> > > This is not supported at the moment if nothing has changed:
>> > >
>> > > https://issues.apache.org/jira/browse/INFRA-11000 <
>> > > https://issues.apache.org/jira/browse/INFRA-11000>
>> > >
>> > > -Flavio
>> > >
>> > > > On 08 Oct 2016, at 00:54, Benjamin Reed  wrote:
>> > > >
>> > > > it doesn't look like we need to setup keys. this seems to work for
>> me:
>> > > >
>> > > > https://git-wip-us.apache.org/#committers-getting-started
>> > > >
>> > > > it does seem strange that we aren't using public keys and that i'm
>> > > sticking
>> > > > a password in .netrc :P i'm wondering if other projects were able to
>> > get
>> > > > this going over ssh.
>> > > >
>> > > > i'll take a whack at cleaning up the svn and subversion references.
>> > > >
>> > > > ben
>> > > >
>> > > > On Fri, Oct 7, 2016 at 12:59 PM, Camille Fournier <
>> cami...@apache.org>
>> > > > wrote:
>> > > >
>> > > >> Hey folks,
>> > > >>
>> > > >> So I'm trying to get in a patch but this has not been updated to
>> tell
>> > > >> committers how to actually get the git keys set up:
>> > > >> https://cwiki.apache.org/confluence/display/ZOOKEEPER/
>> > > Committing+changes
>> > > >>
>> > > >> Can someone float me a link that says how to do this?
>> > > >>
>> > > >> Also a bunch of our documentation still discusses SVN and not git,
>> > which
>> > > >> means we are not done with this migration. If you were pushing for
>> > this
>> > > >> change can you please do some due diligence on the wikis and
>> correct
>> > the
>> > > >> stuff that refers to SVN?
>> > > >>
>> > > >> Thanks,
>> > > >> C
>> > > >>
>> > > >> On Wed, Oct 5, 2016 at 1:02 PM, Edward Ribeiro <
>> > > edward.ribe...@gmail.com>
>> > > >> wrote:
>> > > >>
>> > > >>> Excuse me guys!
>> > > >>>
>> > > >>> I've written on Macbook Pro. No idea why GMail messed it up. I was
>> > only
>> > > >>> able to see the strange characters when I pasted on a gist text
>> area.
>> > > The
>> > > >>> previous message is below, but if anyone is still having trouble
>> (I
>> > > tried
>> > > >>> to remove the weird character), I left a copy at:
>> > > >>> https://gist.github.com/eribeiro/da2a6a6c9a508610d52d0755fae8352d
>> > > >>>
>> > > >>> "Hi,
>> > > >>>
>> > > >>> The patch attached on ZOOKEEPER-2597 is a straightforward
>> adaptation
>> > of
>> > > >>> Kafka's one. It takes care of merging Github PR into Apache git
>> repo
>> > > and
>> > > >> a
>> > > >>> subsequent closing of the PR on the GH side, among other things
>> > > >> (rewriting
>> > > >>> of commit messages, etc). The current status is: the script needs
>> to
>> > be
>> > > >>> reviewed/validated by a committer. It has been some time since I
>> > > uploaded
>> > > >>> the patch, so I gonna do another pass through it in the meantime.
>> > > >>>
>> > > >>> There are some workflow issues beyond the scope of ZOOKEEPER-2597
>> > that
>> > > >> need
>> > > >>> to be sorted out (IMO):
>> > > >>>
>> > > >>> 1. The normal workflow is to open a JIRA ticket before doing any
>> 

[jira] [Commented] (ZOOKEEPER-2597) Add script to merge PR from Apache git repo to Github

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15609163#comment-15609163
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2597:
---

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/85
  
+1 great job Eddie.


> Add script to merge PR from Apache git repo to Github
> -
>
> Key: ZOOKEEPER-2597
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2597
> Project: ZooKeeper
>  Issue Type: Improvement
>Reporter: Edward Ribeiro
>Assignee: Edward Ribeiro
>Priority: Minor
> Attachments: ZOOKEEPER-2597.patch
>
>
> A port of kafka-merge-pr.py to workon on ZooKeeper repo.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] zookeeper issue #85: ZOOKEEPER-2597: Add script to merge PR from Apache git ...

[hanm]

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/85
  
+1 great job Eddie.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2481) Flaky Test: testZeroWeightQuorum

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15609158#comment-15609158
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2481:
---

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/93
  
closing.


> Flaky Test: testZeroWeightQuorum
> 
>
> Key: ZOOKEEPER-2481
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2481
> Project: ZooKeeper
>  Issue Type: Test
>  Components: server, tests
>Affects Versions: 3.4.8, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-test
> Fix For: 3.5.3
>
>
> See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1098/
> {noformat}
> Error Message
> Threads didn't join
> Stacktrace
> junit.framework.AssertionFailedError: Threads didn't join
>   at 
> org.apache.zookeeper.test.FLEZeroWeightTest.testZeroWeightQuorum(FLEZeroWeightTest.java:167)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
> Standard Output
> 2016-07-21 04:24:14,065 [myid:] - INFO  [main:JUnit4ZKTestRunner@47] - No 
> test.method specified. using default methods.
> 2016-07-21 04:24:14,158 [myid:] - INFO  [main:JUnit4ZKTestRunner@47] - No 
> test.method specified. using default methods.
> 2016-07-21 04:24:14,176 [myid:] - INFO  [main:ZKTestCase$1@55] - STARTING 
> testZeroWeightQuorum
> 2016-07-21 04:24:14,180 [myid:] - INFO  
> [main:JUnit4ZKTestRunner$LoggedInvokeMethod@77] - RUNNING TEST METHOD 
> testZeroWeightQuorum
> 2016-07-21 04:24:14,180 [myid:] - INFO  [main:FLEZeroWeightTest@143] - 
> TestZeroWeightQuorum: testZeroWeightQuorum, 9
> 2016-07-21 04:24:14,183 [myid:] - INFO  [main:PortAssignment@157] - Single 
> test process using ports from 11221 - 32767.
> 2016-07-21 04:24:14,187 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11222 from range 11221 - 32767.
> 2016-07-21 04:24:14,189 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11223 from range 11221 - 32767.
> 2016-07-21 04:24:14,189 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11224 from range 11221 - 32767.
> 2016-07-21 04:24:14,218 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11225 from range 11221 - 32767.
> 2016-07-21 04:24:14,218 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11226 from range 11221 - 32767.
> 2016-07-21 04:24:14,219 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11227 from range 11221 - 32767.
> 2016-07-21 04:24:14,219 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11228 from range 11221 - 32767.
> 2016-07-21 04:24:14,220 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11229 from range 11221 - 32767.
> 2016-07-21 04:24:14,220 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11230 from range 11221 - 32767.
> 2016-07-21 04:24:14,221 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11231 from range 11221 - 32767.
> 2016-07-21 04:24:14,224 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11232 from range 11221 - 32767.
> 2016-07-21 04:24:14,224 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11233 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11234 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11235 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11236 from range 11221 - 32767.
> 2016-07-21 04:24:14,226 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11237 from range 11221 - 32767.
> 2016-07-21 04:24:14,226 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11238 from range 11221 - 32767.
> 2016-07-21 04:24:14,227 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11239 from range 11221 - 32767.
> 2016-07-21 04:24:14,227 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11240 from range 11221 - 32767.
> 2016-07-21 04:24:14,228 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11241 from range 11221 - 32767.
> 2016-07-21 04:24:14,228 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11242 from range 11221 - 32767.
> 2016-07-21 04:24:14,229 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11243 from range 11221 - 32767.
> 2016-07-21 04:24:14,229 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11244 from range 11221 - 32767.
> 2016-07-21 04:24:14,229 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11245 from range 11221 - 32767.
> 2016-07-21 04:24:14,230 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11246 from range 11221 - 32767.
> 2016-07-21 04:24:14,230 [myid:] - INFO  

[jira] [Commented] (ZOOKEEPER-2481) Flaky Test: testZeroWeightQuorum

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15609159#comment-15609159
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2481:
---

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/93
  
test on closed comment.


> Flaky Test: testZeroWeightQuorum
> 
>
> Key: ZOOKEEPER-2481
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2481
> Project: ZooKeeper
>  Issue Type: Test
>  Components: server, tests
>Affects Versions: 3.4.8, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-test
> Fix For: 3.5.3
>
>
> See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1098/
> {noformat}
> Error Message
> Threads didn't join
> Stacktrace
> junit.framework.AssertionFailedError: Threads didn't join
>   at 
> org.apache.zookeeper.test.FLEZeroWeightTest.testZeroWeightQuorum(FLEZeroWeightTest.java:167)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
> Standard Output
> 2016-07-21 04:24:14,065 [myid:] - INFO  [main:JUnit4ZKTestRunner@47] - No 
> test.method specified. using default methods.
> 2016-07-21 04:24:14,158 [myid:] - INFO  [main:JUnit4ZKTestRunner@47] - No 
> test.method specified. using default methods.
> 2016-07-21 04:24:14,176 [myid:] - INFO  [main:ZKTestCase$1@55] - STARTING 
> testZeroWeightQuorum
> 2016-07-21 04:24:14,180 [myid:] - INFO  
> [main:JUnit4ZKTestRunner$LoggedInvokeMethod@77] - RUNNING TEST METHOD 
> testZeroWeightQuorum
> 2016-07-21 04:24:14,180 [myid:] - INFO  [main:FLEZeroWeightTest@143] - 
> TestZeroWeightQuorum: testZeroWeightQuorum, 9
> 2016-07-21 04:24:14,183 [myid:] - INFO  [main:PortAssignment@157] - Single 
> test process using ports from 11221 - 32767.
> 2016-07-21 04:24:14,187 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11222 from range 11221 - 32767.
> 2016-07-21 04:24:14,189 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11223 from range 11221 - 32767.
> 2016-07-21 04:24:14,189 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11224 from range 11221 - 32767.
> 2016-07-21 04:24:14,218 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11225 from range 11221 - 32767.
> 2016-07-21 04:24:14,218 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11226 from range 11221 - 32767.
> 2016-07-21 04:24:14,219 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11227 from range 11221 - 32767.
> 2016-07-21 04:24:14,219 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11228 from range 11221 - 32767.
> 2016-07-21 04:24:14,220 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11229 from range 11221 - 32767.
> 2016-07-21 04:24:14,220 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11230 from range 11221 - 32767.
> 2016-07-21 04:24:14,221 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11231 from range 11221 - 32767.
> 2016-07-21 04:24:14,224 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11232 from range 11221 - 32767.
> 2016-07-21 04:24:14,224 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11233 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11234 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11235 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11236 from range 11221 - 32767.
> 2016-07-21 04:24:14,226 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11237 from range 11221 - 32767.
> 2016-07-21 04:24:14,226 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11238 from range 11221 - 32767.
> 2016-07-21 04:24:14,227 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11239 from range 11221 - 32767.
> 2016-07-21 04:24:14,227 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11240 from range 11221 - 32767.
> 2016-07-21 04:24:14,228 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11241 from range 11221 - 32767.
> 2016-07-21 04:24:14,228 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11242 from range 11221 - 32767.
> 2016-07-21 04:24:14,229 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11243 from range 11221 - 32767.
> 2016-07-21 04:24:14,229 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11244 from range 11221 - 32767.
> 2016-07-21 04:24:14,229 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11245 from range 11221 - 32767.
> 2016-07-21 04:24:14,230 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11246 from range 11221 - 32767.
> 2016-07-21 04:24:14,230 [myid:] - INFO  

[jira] [Commented] (ZOOKEEPER-2481) Flaky Test: testZeroWeightQuorum

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15609157#comment-15609157
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2481:
---

Github user hanm closed the pull request at:

https://github.com/apache/zookeeper/pull/93


> Flaky Test: testZeroWeightQuorum
> 
>
> Key: ZOOKEEPER-2481
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2481
> Project: ZooKeeper
>  Issue Type: Test
>  Components: server, tests
>Affects Versions: 3.4.8, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-test
> Fix For: 3.5.3
>
>
> See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1098/
> {noformat}
> Error Message
> Threads didn't join
> Stacktrace
> junit.framework.AssertionFailedError: Threads didn't join
>   at 
> org.apache.zookeeper.test.FLEZeroWeightTest.testZeroWeightQuorum(FLEZeroWeightTest.java:167)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
> Standard Output
> 2016-07-21 04:24:14,065 [myid:] - INFO  [main:JUnit4ZKTestRunner@47] - No 
> test.method specified. using default methods.
> 2016-07-21 04:24:14,158 [myid:] - INFO  [main:JUnit4ZKTestRunner@47] - No 
> test.method specified. using default methods.
> 2016-07-21 04:24:14,176 [myid:] - INFO  [main:ZKTestCase$1@55] - STARTING 
> testZeroWeightQuorum
> 2016-07-21 04:24:14,180 [myid:] - INFO  
> [main:JUnit4ZKTestRunner$LoggedInvokeMethod@77] - RUNNING TEST METHOD 
> testZeroWeightQuorum
> 2016-07-21 04:24:14,180 [myid:] - INFO  [main:FLEZeroWeightTest@143] - 
> TestZeroWeightQuorum: testZeroWeightQuorum, 9
> 2016-07-21 04:24:14,183 [myid:] - INFO  [main:PortAssignment@157] - Single 
> test process using ports from 11221 - 32767.
> 2016-07-21 04:24:14,187 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11222 from range 11221 - 32767.
> 2016-07-21 04:24:14,189 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11223 from range 11221 - 32767.
> 2016-07-21 04:24:14,189 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11224 from range 11221 - 32767.
> 2016-07-21 04:24:14,218 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11225 from range 11221 - 32767.
> 2016-07-21 04:24:14,218 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11226 from range 11221 - 32767.
> 2016-07-21 04:24:14,219 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11227 from range 11221 - 32767.
> 2016-07-21 04:24:14,219 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11228 from range 11221 - 32767.
> 2016-07-21 04:24:14,220 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11229 from range 11221 - 32767.
> 2016-07-21 04:24:14,220 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11230 from range 11221 - 32767.
> 2016-07-21 04:24:14,221 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11231 from range 11221 - 32767.
> 2016-07-21 04:24:14,224 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11232 from range 11221 - 32767.
> 2016-07-21 04:24:14,224 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11233 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11234 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11235 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11236 from range 11221 - 32767.
> 2016-07-21 04:24:14,226 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11237 from range 11221 - 32767.
> 2016-07-21 04:24:14,226 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11238 from range 11221 - 32767.
> 2016-07-21 04:24:14,227 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11239 from range 11221 - 32767.
> 2016-07-21 04:24:14,227 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11240 from range 11221 - 32767.
> 2016-07-21 04:24:14,228 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11241 from range 11221 - 32767.
> 2016-07-21 04:24:14,228 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11242 from range 11221 - 32767.
> 2016-07-21 04:24:14,229 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11243 from range 11221 - 32767.
> 2016-07-21 04:24:14,229 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11244 from range 11221 - 32767.
> 2016-07-21 04:24:14,229 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11245 from range 11221 - 32767.
> 2016-07-21 04:24:14,230 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11246 from range 11221 - 32767.
> 2016-07-21 04:24:14,230 [myid:] - INFO  [main:PortAssignment@85] - 

[GitHub] zookeeper issue #93: ZOOKEEPER-2481: Flaky Test: testZeroWeightQuorum

[hanm]

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/93
  
test on closed comment.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zookeeper issue #93: ZOOKEEPER-2481: Flaky Test: testZeroWeightQuorum

[hanm]

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/93
  
closing.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zookeeper pull request #93: ZOOKEEPER-2481: Flaky Test: testZeroWeightQuorum

[hanm]

Github user hanm closed the pull request at:

https://github.com/apache/zookeeper/pull/93


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2481) Flaky Test: testZeroWeightQuorum

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15609148#comment-15609148
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2481:
---

Github user hanm commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/93#discussion_r85179972
  
--- Diff: README.txt ---
@@ -35,3 +35,7 @@ dist-maven directory are deployed to the central 
repository after the release
 is voted on and approved by the Apache ZooKeeper PMC:
 
   https://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/
+
--- End diff --

5th comment made on git.


> Flaky Test: testZeroWeightQuorum
> 
>
> Key: ZOOKEEPER-2481
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2481
> Project: ZooKeeper
>  Issue Type: Test
>  Components: server, tests
>Affects Versions: 3.4.8, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-test
> Fix For: 3.5.3
>
>
> See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1098/
> {noformat}
> Error Message
> Threads didn't join
> Stacktrace
> junit.framework.AssertionFailedError: Threads didn't join
>   at 
> org.apache.zookeeper.test.FLEZeroWeightTest.testZeroWeightQuorum(FLEZeroWeightTest.java:167)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
> Standard Output
> 2016-07-21 04:24:14,065 [myid:] - INFO  [main:JUnit4ZKTestRunner@47] - No 
> test.method specified. using default methods.
> 2016-07-21 04:24:14,158 [myid:] - INFO  [main:JUnit4ZKTestRunner@47] - No 
> test.method specified. using default methods.
> 2016-07-21 04:24:14,176 [myid:] - INFO  [main:ZKTestCase$1@55] - STARTING 
> testZeroWeightQuorum
> 2016-07-21 04:24:14,180 [myid:] - INFO  
> [main:JUnit4ZKTestRunner$LoggedInvokeMethod@77] - RUNNING TEST METHOD 
> testZeroWeightQuorum
> 2016-07-21 04:24:14,180 [myid:] - INFO  [main:FLEZeroWeightTest@143] - 
> TestZeroWeightQuorum: testZeroWeightQuorum, 9
> 2016-07-21 04:24:14,183 [myid:] - INFO  [main:PortAssignment@157] - Single 
> test process using ports from 11221 - 32767.
> 2016-07-21 04:24:14,187 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11222 from range 11221 - 32767.
> 2016-07-21 04:24:14,189 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11223 from range 11221 - 32767.
> 2016-07-21 04:24:14,189 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11224 from range 11221 - 32767.
> 2016-07-21 04:24:14,218 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11225 from range 11221 - 32767.
> 2016-07-21 04:24:14,218 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11226 from range 11221 - 32767.
> 2016-07-21 04:24:14,219 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11227 from range 11221 - 32767.
> 2016-07-21 04:24:14,219 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11228 from range 11221 - 32767.
> 2016-07-21 04:24:14,220 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11229 from range 11221 - 32767.
> 2016-07-21 04:24:14,220 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11230 from range 11221 - 32767.
> 2016-07-21 04:24:14,221 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11231 from range 11221 - 32767.
> 2016-07-21 04:24:14,224 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11232 from range 11221 - 32767.
> 2016-07-21 04:24:14,224 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11233 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11234 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11235 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11236 from range 11221 - 32767.
> 2016-07-21 04:24:14,226 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11237 from range 11221 - 32767.
> 2016-07-21 04:24:14,226 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11238 from range 11221 - 32767.
> 2016-07-21 04:24:14,227 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11239 from range 11221 - 32767.
> 2016-07-21 04:24:14,227 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11240 from range 11221 - 32767.
> 2016-07-21 04:24:14,228 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11241 from range 11221 - 32767.
> 2016-07-21 04:24:14,228 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11242 from range 11221 - 32767.
> 2016-07-21 04:24:14,229 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11243 from range 11221 - 32767.
> 2016-07-21 04:24:14,229 [myid:] - INFO  [main:PortAssignment@85] 

[jira] [Commented] (ZOOKEEPER-2481) Flaky Test: testZeroWeightQuorum

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15609145#comment-15609145
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2481:
---

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/93
  
4th general comment.


> Flaky Test: testZeroWeightQuorum
> 
>
> Key: ZOOKEEPER-2481
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2481
> Project: ZooKeeper
>  Issue Type: Test
>  Components: server, tests
>Affects Versions: 3.4.8, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-test
> Fix For: 3.5.3
>
>
> See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1098/
> {noformat}
> Error Message
> Threads didn't join
> Stacktrace
> junit.framework.AssertionFailedError: Threads didn't join
>   at 
> org.apache.zookeeper.test.FLEZeroWeightTest.testZeroWeightQuorum(FLEZeroWeightTest.java:167)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
> Standard Output
> 2016-07-21 04:24:14,065 [myid:] - INFO  [main:JUnit4ZKTestRunner@47] - No 
> test.method specified. using default methods.
> 2016-07-21 04:24:14,158 [myid:] - INFO  [main:JUnit4ZKTestRunner@47] - No 
> test.method specified. using default methods.
> 2016-07-21 04:24:14,176 [myid:] - INFO  [main:ZKTestCase$1@55] - STARTING 
> testZeroWeightQuorum
> 2016-07-21 04:24:14,180 [myid:] - INFO  
> [main:JUnit4ZKTestRunner$LoggedInvokeMethod@77] - RUNNING TEST METHOD 
> testZeroWeightQuorum
> 2016-07-21 04:24:14,180 [myid:] - INFO  [main:FLEZeroWeightTest@143] - 
> TestZeroWeightQuorum: testZeroWeightQuorum, 9
> 2016-07-21 04:24:14,183 [myid:] - INFO  [main:PortAssignment@157] - Single 
> test process using ports from 11221 - 32767.
> 2016-07-21 04:24:14,187 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11222 from range 11221 - 32767.
> 2016-07-21 04:24:14,189 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11223 from range 11221 - 32767.
> 2016-07-21 04:24:14,189 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11224 from range 11221 - 32767.
> 2016-07-21 04:24:14,218 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11225 from range 11221 - 32767.
> 2016-07-21 04:24:14,218 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11226 from range 11221 - 32767.
> 2016-07-21 04:24:14,219 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11227 from range 11221 - 32767.
> 2016-07-21 04:24:14,219 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11228 from range 11221 - 32767.
> 2016-07-21 04:24:14,220 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11229 from range 11221 - 32767.
> 2016-07-21 04:24:14,220 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11230 from range 11221 - 32767.
> 2016-07-21 04:24:14,221 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11231 from range 11221 - 32767.
> 2016-07-21 04:24:14,224 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11232 from range 11221 - 32767.
> 2016-07-21 04:24:14,224 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11233 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11234 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11235 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11236 from range 11221 - 32767.
> 2016-07-21 04:24:14,226 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11237 from range 11221 - 32767.
> 2016-07-21 04:24:14,226 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11238 from range 11221 - 32767.
> 2016-07-21 04:24:14,227 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11239 from range 11221 - 32767.
> 2016-07-21 04:24:14,227 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11240 from range 11221 - 32767.
> 2016-07-21 04:24:14,228 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11241 from range 11221 - 32767.
> 2016-07-21 04:24:14,228 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11242 from range 11221 - 32767.
> 2016-07-21 04:24:14,229 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11243 from range 11221 - 32767.
> 2016-07-21 04:24:14,229 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11244 from range 11221 - 32767.
> 2016-07-21 04:24:14,229 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11245 from range 11221 - 32767.
> 2016-07-21 04:24:14,230 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11246 from range 11221 - 32767.
> 2016-07-21 04:24:14,230 [myid:] - INFO  

[GitHub] zookeeper pull request #93: ZOOKEEPER-2481: Flaky Test: testZeroWeightQuorum

[hanm]

Github user hanm commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/93#discussion_r85179972
  
--- Diff: README.txt ---
@@ -35,3 +35,7 @@ dist-maven directory are deployed to the central 
repository after the release
 is voted on and approved by the Apache ZooKeeper PMC:
 
   https://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/
+
--- End diff --

5th comment made on git.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2481) Flaky Test: testZeroWeightQuorum

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15609147#comment-15609147
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2481:
---

Github user hanm commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/93#discussion_r85179943
  
--- Diff: README.txt ---
@@ -35,3 +35,7 @@ dist-maven directory are deployed to the central 
repository after the release
 is voted on and approved by the Apache ZooKeeper PMC:
 
   https://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/
+
--- End diff --

4th comment made on git.


> Flaky Test: testZeroWeightQuorum
> 
>
> Key: ZOOKEEPER-2481
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2481
> Project: ZooKeeper
>  Issue Type: Test
>  Components: server, tests
>Affects Versions: 3.4.8, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-test
> Fix For: 3.5.3
>
>
> See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1098/
> {noformat}
> Error Message
> Threads didn't join
> Stacktrace
> junit.framework.AssertionFailedError: Threads didn't join
>   at 
> org.apache.zookeeper.test.FLEZeroWeightTest.testZeroWeightQuorum(FLEZeroWeightTest.java:167)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
> Standard Output
> 2016-07-21 04:24:14,065 [myid:] - INFO  [main:JUnit4ZKTestRunner@47] - No 
> test.method specified. using default methods.
> 2016-07-21 04:24:14,158 [myid:] - INFO  [main:JUnit4ZKTestRunner@47] - No 
> test.method specified. using default methods.
> 2016-07-21 04:24:14,176 [myid:] - INFO  [main:ZKTestCase$1@55] - STARTING 
> testZeroWeightQuorum
> 2016-07-21 04:24:14,180 [myid:] - INFO  
> [main:JUnit4ZKTestRunner$LoggedInvokeMethod@77] - RUNNING TEST METHOD 
> testZeroWeightQuorum
> 2016-07-21 04:24:14,180 [myid:] - INFO  [main:FLEZeroWeightTest@143] - 
> TestZeroWeightQuorum: testZeroWeightQuorum, 9
> 2016-07-21 04:24:14,183 [myid:] - INFO  [main:PortAssignment@157] - Single 
> test process using ports from 11221 - 32767.
> 2016-07-21 04:24:14,187 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11222 from range 11221 - 32767.
> 2016-07-21 04:24:14,189 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11223 from range 11221 - 32767.
> 2016-07-21 04:24:14,189 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11224 from range 11221 - 32767.
> 2016-07-21 04:24:14,218 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11225 from range 11221 - 32767.
> 2016-07-21 04:24:14,218 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11226 from range 11221 - 32767.
> 2016-07-21 04:24:14,219 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11227 from range 11221 - 32767.
> 2016-07-21 04:24:14,219 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11228 from range 11221 - 32767.
> 2016-07-21 04:24:14,220 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11229 from range 11221 - 32767.
> 2016-07-21 04:24:14,220 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11230 from range 11221 - 32767.
> 2016-07-21 04:24:14,221 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11231 from range 11221 - 32767.
> 2016-07-21 04:24:14,224 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11232 from range 11221 - 32767.
> 2016-07-21 04:24:14,224 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11233 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11234 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11235 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11236 from range 11221 - 32767.
> 2016-07-21 04:24:14,226 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11237 from range 11221 - 32767.
> 2016-07-21 04:24:14,226 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11238 from range 11221 - 32767.
> 2016-07-21 04:24:14,227 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11239 from range 11221 - 32767.
> 2016-07-21 04:24:14,227 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11240 from range 11221 - 32767.
> 2016-07-21 04:24:14,228 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11241 from range 11221 - 32767.
> 2016-07-21 04:24:14,228 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11242 from range 11221 - 32767.
> 2016-07-21 04:24:14,229 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11243 from range 11221 - 32767.
> 2016-07-21 04:24:14,229 [myid:] - INFO  [main:PortAssignment@85] 

[GitHub] zookeeper pull request #93: ZOOKEEPER-2481: Flaky Test: testZeroWeightQuorum

[hanm]

Github user hanm commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/93#discussion_r85179943
  
--- Diff: README.txt ---
@@ -35,3 +35,7 @@ dist-maven directory are deployed to the central 
repository after the release
 is voted on and approved by the Apache ZooKeeper PMC:
 
   https://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/
+
--- End diff --

4th comment made on git.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zookeeper issue #93: ZOOKEEPER-2481: Flaky Test: testZeroWeightQuorum

[hanm]

Github user hanm commented on the issue:

https://github.com/apache/zookeeper/pull/93
  
4th general comment.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

ZooKeeper_branch35_solaris - Build # 297 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_solaris/297/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 432606 lines...]
[junit] 2016-10-26 17:15:34,835 [myid:] - INFO  [main:ClientBase@386] - 
CREATING server instance 127.0.0.1:11222
[junit] 2016-10-26 17:15:34,835 [myid:] - INFO  
[main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s 
sessionless connection timeout, 2 selector thread(s), 16 worker threads, and 64 
kB direct buffers.
[junit] 2016-10-26 17:15:34,836 [myid:] - INFO  
[main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222
[junit] 2016-10-26 17:15:34,837 [myid:] - INFO  [main:ClientBase@361] - 
STARTING server instance 127.0.0.1:11222
[junit] 2016-10-26 17:15:34,837 [myid:] - INFO  [main:ZooKeeperServer@889] 
- minSessionTimeout set to 6000
[junit] 2016-10-26 17:15:34,837 [myid:] - INFO  [main:ZooKeeperServer@898] 
- maxSessionTimeout set to 6
[junit] 2016-10-26 17:15:34,837 [myid:] - INFO  [main:ZooKeeperServer@159] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test9182599278906332444.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test9182599278906332444.junit.dir/version-2
[junit] 2016-10-26 17:15:34,838 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test9182599278906332444.junit.dir/version-2/snapshot.b
[junit] 2016-10-26 17:15:34,840 [myid:] - INFO  [main:FileTxnSnapLog@306] - 
Snapshotting: 0xb to 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/build/test/tmp/test9182599278906332444.junit.dir/version-2/snapshot.b
[junit] 2016-10-26 17:15:34,841 [myid:] - ERROR [main:ZooKeeperServer@501] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-10-26 17:15:34,841 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-10-26 17:15:34,842 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:57443
[junit] 2016-10-26 17:15:34,842 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:57443
[junit] 2016-10-26 17:15:34,843 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2016-10-26 17:15:34,843 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:57443 (no session established for client)
[junit] 2016-10-26 17:15:34,843 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-10-26 17:15:34,845 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2016-10-26 17:15:34,845 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2016-10-26 17:15:34,845 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2016-10-26 17:15:34,845 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2016-10-26 17:15:34,845 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17682
[junit] 2016-10-26 17:15:34,845 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24
[junit] 2016-10-26 17:15:34,846 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2016-10-26 17:15:34,846 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2016-10-26 17:15:34,922 [myid:] - INFO  [main:ZooKeeper@1313] - 
Session: 0x1247ef81d70 closed
[junit] 2016-10-26 17:15:34,922 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2016-10-26 17:15:34,922 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1247ef81d70
[junit] 2016-10-26 17:15:34,923 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-10-26 17:15:34,922 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-10-26 17:15:34,922 [myid:] - INFO  

[jira] [Commented] (ZOOKEEPER-2481) Flaky Test: testZeroWeightQuorum

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15609043#comment-15609043
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2481:
---

Github user hanm commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/93#discussion_r85172473
  
--- Diff: README.txt ---
@@ -35,3 +35,7 @@ dist-maven directory are deployed to the central 
repository after the release
 is voted on and approved by the Apache ZooKeeper PMC:
 
   https://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/
+
--- End diff --

3rd comment made on git.


> Flaky Test: testZeroWeightQuorum
> 
>
> Key: ZOOKEEPER-2481
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2481
> Project: ZooKeeper
>  Issue Type: Test
>  Components: server, tests
>Affects Versions: 3.4.8, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-test
> Fix For: 3.5.3
>
>
> See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1098/
> {noformat}
> Error Message
> Threads didn't join
> Stacktrace
> junit.framework.AssertionFailedError: Threads didn't join
>   at 
> org.apache.zookeeper.test.FLEZeroWeightTest.testZeroWeightQuorum(FLEZeroWeightTest.java:167)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
> Standard Output
> 2016-07-21 04:24:14,065 [myid:] - INFO  [main:JUnit4ZKTestRunner@47] - No 
> test.method specified. using default methods.
> 2016-07-21 04:24:14,158 [myid:] - INFO  [main:JUnit4ZKTestRunner@47] - No 
> test.method specified. using default methods.
> 2016-07-21 04:24:14,176 [myid:] - INFO  [main:ZKTestCase$1@55] - STARTING 
> testZeroWeightQuorum
> 2016-07-21 04:24:14,180 [myid:] - INFO  
> [main:JUnit4ZKTestRunner$LoggedInvokeMethod@77] - RUNNING TEST METHOD 
> testZeroWeightQuorum
> 2016-07-21 04:24:14,180 [myid:] - INFO  [main:FLEZeroWeightTest@143] - 
> TestZeroWeightQuorum: testZeroWeightQuorum, 9
> 2016-07-21 04:24:14,183 [myid:] - INFO  [main:PortAssignment@157] - Single 
> test process using ports from 11221 - 32767.
> 2016-07-21 04:24:14,187 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11222 from range 11221 - 32767.
> 2016-07-21 04:24:14,189 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11223 from range 11221 - 32767.
> 2016-07-21 04:24:14,189 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11224 from range 11221 - 32767.
> 2016-07-21 04:24:14,218 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11225 from range 11221 - 32767.
> 2016-07-21 04:24:14,218 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11226 from range 11221 - 32767.
> 2016-07-21 04:24:14,219 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11227 from range 11221 - 32767.
> 2016-07-21 04:24:14,219 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11228 from range 11221 - 32767.
> 2016-07-21 04:24:14,220 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11229 from range 11221 - 32767.
> 2016-07-21 04:24:14,220 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11230 from range 11221 - 32767.
> 2016-07-21 04:24:14,221 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11231 from range 11221 - 32767.
> 2016-07-21 04:24:14,224 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11232 from range 11221 - 32767.
> 2016-07-21 04:24:14,224 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11233 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11234 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11235 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11236 from range 11221 - 32767.
> 2016-07-21 04:24:14,226 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11237 from range 11221 - 32767.
> 2016-07-21 04:24:14,226 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11238 from range 11221 - 32767.
> 2016-07-21 04:24:14,227 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11239 from range 11221 - 32767.
> 2016-07-21 04:24:14,227 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11240 from range 11221 - 32767.
> 2016-07-21 04:24:14,228 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11241 from range 11221 - 32767.
> 2016-07-21 04:24:14,228 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11242 from range 11221 - 32767.
> 2016-07-21 04:24:14,229 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11243 from range 11221 - 32767.
> 2016-07-21 04:24:14,229 [myid:] - INFO  [main:PortAssignment@85] 

[GitHub] zookeeper pull request #93: ZOOKEEPER-2481: Flaky Test: testZeroWeightQuorum

[hanm]

Github user hanm commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/93#discussion_r85172473
  
--- Diff: README.txt ---
@@ -35,3 +35,7 @@ dist-maven directory are deployed to the central 
repository after the release
 is voted on and approved by the Apache ZooKeeper PMC:
 
   https://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/
+
--- End diff --

3rd comment made on git.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2481) Flaky Test: testZeroWeightQuorum

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15609035#comment-15609035
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2481:
---

Github user hanm commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/93#discussion_r85172091
  
--- Diff: README.txt ---
@@ -35,3 +35,7 @@ dist-maven directory are deployed to the central 
repository after the release
 is voted on and approved by the Apache ZooKeeper PMC:
 
   https://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/
+
--- End diff --

This is a comment made on git.


> Flaky Test: testZeroWeightQuorum
> 
>
> Key: ZOOKEEPER-2481
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2481
> Project: ZooKeeper
>  Issue Type: Test
>  Components: server, tests
>Affects Versions: 3.4.8, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-test
> Fix For: 3.5.3
>
>
> See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1098/
> {noformat}
> Error Message
> Threads didn't join
> Stacktrace
> junit.framework.AssertionFailedError: Threads didn't join
>   at 
> org.apache.zookeeper.test.FLEZeroWeightTest.testZeroWeightQuorum(FLEZeroWeightTest.java:167)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
> Standard Output
> 2016-07-21 04:24:14,065 [myid:] - INFO  [main:JUnit4ZKTestRunner@47] - No 
> test.method specified. using default methods.
> 2016-07-21 04:24:14,158 [myid:] - INFO  [main:JUnit4ZKTestRunner@47] - No 
> test.method specified. using default methods.
> 2016-07-21 04:24:14,176 [myid:] - INFO  [main:ZKTestCase$1@55] - STARTING 
> testZeroWeightQuorum
> 2016-07-21 04:24:14,180 [myid:] - INFO  
> [main:JUnit4ZKTestRunner$LoggedInvokeMethod@77] - RUNNING TEST METHOD 
> testZeroWeightQuorum
> 2016-07-21 04:24:14,180 [myid:] - INFO  [main:FLEZeroWeightTest@143] - 
> TestZeroWeightQuorum: testZeroWeightQuorum, 9
> 2016-07-21 04:24:14,183 [myid:] - INFO  [main:PortAssignment@157] - Single 
> test process using ports from 11221 - 32767.
> 2016-07-21 04:24:14,187 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11222 from range 11221 - 32767.
> 2016-07-21 04:24:14,189 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11223 from range 11221 - 32767.
> 2016-07-21 04:24:14,189 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11224 from range 11221 - 32767.
> 2016-07-21 04:24:14,218 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11225 from range 11221 - 32767.
> 2016-07-21 04:24:14,218 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11226 from range 11221 - 32767.
> 2016-07-21 04:24:14,219 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11227 from range 11221 - 32767.
> 2016-07-21 04:24:14,219 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11228 from range 11221 - 32767.
> 2016-07-21 04:24:14,220 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11229 from range 11221 - 32767.
> 2016-07-21 04:24:14,220 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11230 from range 11221 - 32767.
> 2016-07-21 04:24:14,221 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11231 from range 11221 - 32767.
> 2016-07-21 04:24:14,224 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11232 from range 11221 - 32767.
> 2016-07-21 04:24:14,224 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11233 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11234 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11235 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11236 from range 11221 - 32767.
> 2016-07-21 04:24:14,226 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11237 from range 11221 - 32767.
> 2016-07-21 04:24:14,226 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11238 from range 11221 - 32767.
> 2016-07-21 04:24:14,227 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11239 from range 11221 - 32767.
> 2016-07-21 04:24:14,227 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11240 from range 11221 - 32767.
> 2016-07-21 04:24:14,228 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11241 from range 11221 - 32767.
> 2016-07-21 04:24:14,228 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11242 from range 11221 - 32767.
> 2016-07-21 04:24:14,229 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11243 from range 11221 - 32767.
> 2016-07-21 04:24:14,229 [myid:] - INFO  

[GitHub] zookeeper pull request #93: ZOOKEEPER-2481: Flaky Test: testZeroWeightQuorum

[hanm]

GitHub user hanm opened a pull request:

https://github.com/apache/zookeeper/pull/93

ZOOKEEPER-2481: Flaky Test: testZeroWeightQuorum

Don't merge, this is just a test please discard. 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/hanm/zookeeper ZOOKEEPER-2481

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zookeeper/pull/93.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #93


commit b0c87dbd0ec070195c8a4f98e88d33ff567230ca
Author: Michael Han 
Date:   2016-10-17T21:13:19Z

This is just a test please discard.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zookeeper pull request #93: ZOOKEEPER-2481: Flaky Test: testZeroWeightQuorum

[hanm]

Github user hanm commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/93#discussion_r85172091
  
--- Diff: README.txt ---
@@ -35,3 +35,7 @@ dist-maven directory are deployed to the central 
repository after the release
 is voted on and approved by the Apache ZooKeeper PMC:
 
   https://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/
+
--- End diff --

This is a comment made on git.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (ZOOKEEPER-2481) Flaky Test: testZeroWeightQuorum

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15609033#comment-15609033
 ] 

ASF GitHub Bot commented on ZOOKEEPER-2481:
---

GitHub user hanm opened a pull request:

https://github.com/apache/zookeeper/pull/93

ZOOKEEPER-2481: Flaky Test: testZeroWeightQuorum

Don't merge, this is just a test please discard. 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/hanm/zookeeper ZOOKEEPER-2481

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zookeeper/pull/93.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #93


commit b0c87dbd0ec070195c8a4f98e88d33ff567230ca
Author: Michael Han 
Date:   2016-10-17T21:13:19Z

This is just a test please discard.




> Flaky Test: testZeroWeightQuorum
> 
>
> Key: ZOOKEEPER-2481
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2481
> Project: ZooKeeper
>  Issue Type: Test
>  Components: server, tests
>Affects Versions: 3.4.8, 3.5.2
>Reporter: Michael Han
>Assignee: Michael Han
>  Labels: flaky, flaky-test
> Fix For: 3.5.3
>
>
> See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1098/
> {noformat}
> Error Message
> Threads didn't join
> Stacktrace
> junit.framework.AssertionFailedError: Threads didn't join
>   at 
> org.apache.zookeeper.test.FLEZeroWeightTest.testZeroWeightQuorum(FLEZeroWeightTest.java:167)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
> Standard Output
> 2016-07-21 04:24:14,065 [myid:] - INFO  [main:JUnit4ZKTestRunner@47] - No 
> test.method specified. using default methods.
> 2016-07-21 04:24:14,158 [myid:] - INFO  [main:JUnit4ZKTestRunner@47] - No 
> test.method specified. using default methods.
> 2016-07-21 04:24:14,176 [myid:] - INFO  [main:ZKTestCase$1@55] - STARTING 
> testZeroWeightQuorum
> 2016-07-21 04:24:14,180 [myid:] - INFO  
> [main:JUnit4ZKTestRunner$LoggedInvokeMethod@77] - RUNNING TEST METHOD 
> testZeroWeightQuorum
> 2016-07-21 04:24:14,180 [myid:] - INFO  [main:FLEZeroWeightTest@143] - 
> TestZeroWeightQuorum: testZeroWeightQuorum, 9
> 2016-07-21 04:24:14,183 [myid:] - INFO  [main:PortAssignment@157] - Single 
> test process using ports from 11221 - 32767.
> 2016-07-21 04:24:14,187 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11222 from range 11221 - 32767.
> 2016-07-21 04:24:14,189 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11223 from range 11221 - 32767.
> 2016-07-21 04:24:14,189 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11224 from range 11221 - 32767.
> 2016-07-21 04:24:14,218 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11225 from range 11221 - 32767.
> 2016-07-21 04:24:14,218 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11226 from range 11221 - 32767.
> 2016-07-21 04:24:14,219 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11227 from range 11221 - 32767.
> 2016-07-21 04:24:14,219 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11228 from range 11221 - 32767.
> 2016-07-21 04:24:14,220 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11229 from range 11221 - 32767.
> 2016-07-21 04:24:14,220 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11230 from range 11221 - 32767.
> 2016-07-21 04:24:14,221 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11231 from range 11221 - 32767.
> 2016-07-21 04:24:14,224 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11232 from range 11221 - 32767.
> 2016-07-21 04:24:14,224 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11233 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11234 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11235 from range 11221 - 32767.
> 2016-07-21 04:24:14,225 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11236 from range 11221 - 32767.
> 2016-07-21 04:24:14,226 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11237 from range 11221 - 32767.
> 2016-07-21 04:24:14,226 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11238 from range 11221 - 32767.
> 2016-07-21 04:24:14,227 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11239 from range 11221 - 32767.
> 2016-07-21 04:24:14,227 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11240 from range 11221 - 32767.
> 2016-07-21 04:24:14,228 [myid:] - INFO  [main:PortAssignment@85] - Assigned 
> port 11241 from range 

Re: [VOTE] move Apache Zookeeper to git

[Michael Han]

>> The git PR *review* comments for ZOOKEEPER-2597 didn't show up on JIRA.

The bridge was working the day Infra made the change - see the previous
comments made by git bot on ZOOKEEPER-761. Now it seems stop working. I am
reopening INFRA-12752 and building a case.

On Wed, Oct 26, 2016 at 9:45 AM, Edward Ribeiro 
wrote:

> Dear community,
>
> The zk-merger-pr.py script has been merged into master (thanks a LOT Ben
> Reed for reviewing/discussing/testing and commiting):
> https://issues.apache.org/jira/browse/ZOOKEEPER-2597
>
> As stated in the issue and on GH, this tool is a modified version of
> similar tools from Kafka, that is a copy of a Spark's one. It has some
> rough edges so we will certainly benefit from further enhancements and
> fixes. I changed the smallest possible pieces of code, just to make it work
> on a ZK repo so the credits go to the original authors.
>
> Some notes:
>
> 1. The git PR *review* comments for ZOOKEEPER-2597 didn't show up on JIRA.
> Only the opening and closing of the issue. Can we double check this as
> INFRA-12752 is closed, Michael Han?
>
> 2. I scribbled a draft on how use the tool at
> https://docs.google.com/document/d/1i00ZXjrW2fu17vr_
> h7F1bUrqXg3urw4Hm7KirQDpPIU/edit
>  (still very crude, but feel free to improve it). I would like to move this
> text to https://cwiki.apache.org/confluence/display/ZOOKEEPER/Index but
> looks like I don't have permission to create a page there yet. Any help?
>
> Best regards,
> Eddie
>
> On Sat, Oct 22, 2016 at 7:08 PM, Michael Han  wrote:
>
> > FYI infra did some work in INFRA-12752 and the git PR comments can be
> > pushed to Apache JIRA.
> >
> > On Sat, Oct 8, 2016 at 8:01 AM, Flavio Junqueira  wrote:
> >
> > > This is not supported at the moment if nothing has changed:
> > >
> > > https://issues.apache.org/jira/browse/INFRA-11000 <
> > > https://issues.apache.org/jira/browse/INFRA-11000>
> > >
> > > -Flavio
> > >
> > > > On 08 Oct 2016, at 00:54, Benjamin Reed  wrote:
> > > >
> > > > it doesn't look like we need to setup keys. this seems to work for
> me:
> > > >
> > > > https://git-wip-us.apache.org/#committers-getting-started
> > > >
> > > > it does seem strange that we aren't using public keys and that i'm
> > > sticking
> > > > a password in .netrc :P i'm wondering if other projects were able to
> > get
> > > > this going over ssh.
> > > >
> > > > i'll take a whack at cleaning up the svn and subversion references.
> > > >
> > > > ben
> > > >
> > > > On Fri, Oct 7, 2016 at 12:59 PM, Camille Fournier <
> cami...@apache.org>
> > > > wrote:
> > > >
> > > >> Hey folks,
> > > >>
> > > >> So I'm trying to get in a patch but this has not been updated to
> tell
> > > >> committers how to actually get the git keys set up:
> > > >> https://cwiki.apache.org/confluence/display/ZOOKEEPER/
> > > Committing+changes
> > > >>
> > > >> Can someone float me a link that says how to do this?
> > > >>
> > > >> Also a bunch of our documentation still discusses SVN and not git,
> > which
> > > >> means we are not done with this migration. If you were pushing for
> > this
> > > >> change can you please do some due diligence on the wikis and correct
> > the
> > > >> stuff that refers to SVN?
> > > >>
> > > >> Thanks,
> > > >> C
> > > >>
> > > >> On Wed, Oct 5, 2016 at 1:02 PM, Edward Ribeiro <
> > > edward.ribe...@gmail.com>
> > > >> wrote:
> > > >>
> > > >>> Excuse me guys!
> > > >>>
> > > >>> I've written on Macbook Pro. No idea why GMail messed it up. I was
> > only
> > > >>> able to see the strange characters when I pasted on a gist text
> area.
> > > The
> > > >>> previous message is below, but if anyone is still having trouble (I
> > > tried
> > > >>> to remove the weird character), I left a copy at:
> > > >>> https://gist.github.com/eribeiro/da2a6a6c9a508610d52d0755fae8352d
> > > >>>
> > > >>> "Hi,
> > > >>>
> > > >>> The patch attached on ZOOKEEPER-2597 is a straightforward
> adaptation
> > of
> > > >>> Kafka's one. It takes care of merging Github PR into Apache git
> repo
> > > and
> > > >> a
> > > >>> subsequent closing of the PR on the GH side, among other things
> > > >> (rewriting
> > > >>> of commit messages, etc). The current status is: the script needs
> to
> > be
> > > >>> reviewed/validated by a committer. It has been some time since I
> > > uploaded
> > > >>> the patch, so I gonna do another pass through it in the meantime.
> > > >>>
> > > >>> There are some workflow issues beyond the scope of ZOOKEEPER-2597
> > that
> > > >> need
> > > >>> to be sorted out (IMO):
> > > >>>
> > > >>> 1. The normal workflow is to open a JIRA ticket before doing any GH
> > PR,
> > > >>> that is, no JIRA-less PRs. The PR should have a title of the form
> > > >>> "ZOOKEEPER-: Title". This will trigger the Apache JIRA-Github
> > > >>> integration and it's opening show up in the JIRA ticket.
> > > >>>
> > > >>> 2. OTOH, not every Kafka PR needs a corresponding JIRA 

Re: [VOTE] move Apache Zookeeper to git

[Flavio Junqueira]

Thanks, Eddie. This is great.

> On 26 Oct 2016, at 17:45, Edward Ribeiro  wrote:
> (still very crude, but feel free to improve it). I would like to move this
> text to https://cwiki.apache.org/confluence/display/ZOOKEEPER/Index but
> looks like I don't have permission to create a page there yet. Any help?
> 

Done.

-Flavio

> 
> On Sat, Oct 22, 2016 at 7:08 PM, Michael Han  wrote:
> 
>> FYI infra did some work in INFRA-12752 and the git PR comments can be
>> pushed to Apache JIRA.
>> 
>> On Sat, Oct 8, 2016 at 8:01 AM, Flavio Junqueira  wrote:
>> 
>>> This is not supported at the moment if nothing has changed:
>>> 
>>> https://issues.apache.org/jira/browse/INFRA-11000 <
>>> https://issues.apache.org/jira/browse/INFRA-11000>
>>> 
>>> -Flavio
>>> 
 On 08 Oct 2016, at 00:54, Benjamin Reed  wrote:
 
 it doesn't look like we need to setup keys. this seems to work for me:
 
 https://git-wip-us.apache.org/#committers-getting-started
 
 it does seem strange that we aren't using public keys and that i'm
>>> sticking
 a password in .netrc :P i'm wondering if other projects were able to
>> get
 this going over ssh.
 
 i'll take a whack at cleaning up the svn and subversion references.
 
 ben
 
 On Fri, Oct 7, 2016 at 12:59 PM, Camille Fournier 
 wrote:
 
> Hey folks,
> 
> So I'm trying to get in a patch but this has not been updated to tell
> committers how to actually get the git keys set up:
> https://cwiki.apache.org/confluence/display/ZOOKEEPER/
>>> Committing+changes
> 
> Can someone float me a link that says how to do this?
> 
> Also a bunch of our documentation still discusses SVN and not git,
>> which
> means we are not done with this migration. If you were pushing for
>> this
> change can you please do some due diligence on the wikis and correct
>> the
> stuff that refers to SVN?
> 
> Thanks,
> C
> 
> On Wed, Oct 5, 2016 at 1:02 PM, Edward Ribeiro <
>>> edward.ribe...@gmail.com>
> wrote:
> 
>> Excuse me guys!
>> 
>> I've written on Macbook Pro. No idea why GMail messed it up. I was
>> only
>> able to see the strange characters when I pasted on a gist text area.
>>> The
>> previous message is below, but if anyone is still having trouble (I
>>> tried
>> to remove the weird character), I left a copy at:
>> https://gist.github.com/eribeiro/da2a6a6c9a508610d52d0755fae8352d
>> 
>> "Hi,
>> 
>> The patch attached on ZOOKEEPER-2597 is a straightforward adaptation
>> of
>> Kafka's one. It takes care of merging Github PR into Apache git repo
>>> and
> a
>> subsequent closing of the PR on the GH side, among other things
> (rewriting
>> of commit messages, etc). The current status is: the script needs to
>> be
>> reviewed/validated by a committer. It has been some time since I
>>> uploaded
>> the patch, so I gonna do another pass through it in the meantime.
>> 
>> There are some workflow issues beyond the scope of ZOOKEEPER-2597
>> that
> need
>> to be sorted out (IMO):
>> 
>> 1. The normal workflow is to open a JIRA ticket before doing any GH
>> PR,
>> that is, no JIRA-less PRs. The PR should have a title of the form
>> "ZOOKEEPER-: Title". This will trigger the Apache JIRA-Github
>> integration and it's opening show up in the JIRA ticket.
>> 
>> 2. OTOH, not every Kafka PR needs a corresponding JIRA ticket. There
>>> are
> a
>> class of PRs with "MINOR" title that represent trivial code changes
>> and
>> "HOT-FIX" title that fix urgent, but simple bugs. Both bypass the
>> JIRA
>> creation step, even tough they are still subject to review. It's
>> worth
>> adopting a similar approach for ZK project?
>> 
>> 3. IIRC (didn't find any page to confirm), Cassandra project
>>> encourages,
>> but not demands, that contributors also upload a patch file to JIRA
>>> even
> in
>> the case of a GH PR (as to leave a audit trail, I guess). Or, at
>>> least,
> C*
>> project leaves up to the contributors to either open a GH PR or
>> upload
> the
>> patch file to JIRA.
>> 
>> 
>> +1 about having a 'paper trail' of review comments on JIRA and/or
>>> mailing
>> list (I would prefer the mailing list tbh). But as Michael and Flavio
>> pointed out, I never seen GH PR review **comments** being written
>> back
>>> to
>> JIRA, at least not in Kafka, Cassandra or Solr projects, that I have
>> followed more closely.
>> 
>> Eddie"
>> 
>> 
>> On Wed, Oct 5, 2016 at 1:35 PM, Michael Han 
>> wrote:
>> 
>>> Eddie's mail contains lots of '=E2=80=8B'' which is unicode
>> character
>>> zero-width space, which might cause parsing trouble for some mail
>> 

Re: [VOTE] move Apache Zookeeper to git

[Edward Ribeiro]

Dear community,

The zk-merger-pr.py script has been merged into master (thanks a LOT Ben
Reed for reviewing/discussing/testing and commiting):
https://issues.apache.org/jira/browse/ZOOKEEPER-2597

As stated in the issue and on GH, this tool is a modified version of
similar tools from Kafka, that is a copy of a Spark's one. It has some
rough edges so we will certainly benefit from further enhancements and
fixes. I changed the smallest possible pieces of code, just to make it work
on a ZK repo so the credits go to the original authors.

Some notes:

1. The git PR *review* comments for ZOOKEEPER-2597 didn't show up on JIRA.
Only the opening and closing of the issue. Can we double check this as
INFRA-12752 is closed, Michael Han?

2. I scribbled a draft on how use the tool at
https://docs.google.com/document/d/1i00ZXjrW2fu17vr_h7F1bUrqXg3urw4Hm7KirQDpPIU/edit
 (still very crude, but feel free to improve it). I would like to move this
text to https://cwiki.apache.org/confluence/display/ZOOKEEPER/Index but
looks like I don't have permission to create a page there yet. Any help?

Best regards,
Eddie

On Sat, Oct 22, 2016 at 7:08 PM, Michael Han  wrote:

> FYI infra did some work in INFRA-12752 and the git PR comments can be
> pushed to Apache JIRA.
>
> On Sat, Oct 8, 2016 at 8:01 AM, Flavio Junqueira  wrote:
>
> > This is not supported at the moment if nothing has changed:
> >
> > https://issues.apache.org/jira/browse/INFRA-11000 <
> > https://issues.apache.org/jira/browse/INFRA-11000>
> >
> > -Flavio
> >
> > > On 08 Oct 2016, at 00:54, Benjamin Reed  wrote:
> > >
> > > it doesn't look like we need to setup keys. this seems to work for me:
> > >
> > > https://git-wip-us.apache.org/#committers-getting-started
> > >
> > > it does seem strange that we aren't using public keys and that i'm
> > sticking
> > > a password in .netrc :P i'm wondering if other projects were able to
> get
> > > this going over ssh.
> > >
> > > i'll take a whack at cleaning up the svn and subversion references.
> > >
> > > ben
> > >
> > > On Fri, Oct 7, 2016 at 12:59 PM, Camille Fournier 
> > > wrote:
> > >
> > >> Hey folks,
> > >>
> > >> So I'm trying to get in a patch but this has not been updated to tell
> > >> committers how to actually get the git keys set up:
> > >> https://cwiki.apache.org/confluence/display/ZOOKEEPER/
> > Committing+changes
> > >>
> > >> Can someone float me a link that says how to do this?
> > >>
> > >> Also a bunch of our documentation still discusses SVN and not git,
> which
> > >> means we are not done with this migration. If you were pushing for
> this
> > >> change can you please do some due diligence on the wikis and correct
> the
> > >> stuff that refers to SVN?
> > >>
> > >> Thanks,
> > >> C
> > >>
> > >> On Wed, Oct 5, 2016 at 1:02 PM, Edward Ribeiro <
> > edward.ribe...@gmail.com>
> > >> wrote:
> > >>
> > >>> Excuse me guys!
> > >>>
> > >>> I've written on Macbook Pro. No idea why GMail messed it up. I was
> only
> > >>> able to see the strange characters when I pasted on a gist text area.
> > The
> > >>> previous message is below, but if anyone is still having trouble (I
> > tried
> > >>> to remove the weird character), I left a copy at:
> > >>> https://gist.github.com/eribeiro/da2a6a6c9a508610d52d0755fae8352d
> > >>>
> > >>> "Hi,
> > >>>
> > >>> The patch attached on ZOOKEEPER-2597 is a straightforward adaptation
> of
> > >>> Kafka's one. It takes care of merging Github PR into Apache git repo
> > and
> > >> a
> > >>> subsequent closing of the PR on the GH side, among other things
> > >> (rewriting
> > >>> of commit messages, etc). The current status is: the script needs to
> be
> > >>> reviewed/validated by a committer. It has been some time since I
> > uploaded
> > >>> the patch, so I gonna do another pass through it in the meantime.
> > >>>
> > >>> There are some workflow issues beyond the scope of ZOOKEEPER-2597
> that
> > >> need
> > >>> to be sorted out (IMO):
> > >>>
> > >>> 1. The normal workflow is to open a JIRA ticket before doing any GH
> PR,
> > >>> that is, no JIRA-less PRs. The PR should have a title of the form
> > >>> "ZOOKEEPER-: Title". This will trigger the Apache JIRA-Github
> > >>> integration and it's opening show up in the JIRA ticket.
> > >>>
> > >>> 2. OTOH, not every Kafka PR needs a corresponding JIRA ticket. There
> > are
> > >> a
> > >>> class of PRs with "MINOR" title that represent trivial code changes
> and
> > >>> "HOT-FIX" title that fix urgent, but simple bugs. Both bypass the
> JIRA
> > >>> creation step, even tough they are still subject to review. It's
> worth
> > >>> adopting a similar approach for ZK project?
> > >>>
> > >>> 3. IIRC (didn't find any page to confirm), Cassandra project
> > encourages,
> > >>> but not demands, that contributors also upload a patch file to JIRA
> > even
> > >> in
> > >>> the case of a GH PR (as to leave a audit trail, I guess). Or, at
> > least,
> > >> C*

[jira] [Updated] (ZOOKEEPER-2621) ZooKeeper doesn't start on MINGW32 (Windows)

[Amichai Rothman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amichai Rothman updated ZOOKEEPER-2621:
---
Attachment: ZOOKEEPER-2621.patch

> ZooKeeper doesn't start on MINGW32 (Windows)
> 
>
> Key: ZOOKEEPER-2621
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2621
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 3.4.9
> Environment: MINGW32_NT-6.1 on Windows 7 (e.g. git bash)
>Reporter: Amichai Rothman
>Assignee: Amichai Rothman
> Attachments: ZOOKEEPER-2621.patch
>
>
> The ZooKeeper scripts fail due to missing cygpath path conversion in a 
> MINGW32 environment, such as when running from git bash (installed by default 
> when installing Git for Windows).
> The fix is to add the line
> {quote}
> MINGW*) cygwin=true ;;
> {quote}
> near the bottom of the zkEnv.sh script, in the case statement that checks for 
> a cygwin environment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2621) ZooKeeper doesn't start on MINGW32 (Windows)

[Flavio Junqueira (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flavio Junqueira updated ZOOKEEPER-2621:

Assignee: Amichai Rothman

> ZooKeeper doesn't start on MINGW32 (Windows)
> 
>
> Key: ZOOKEEPER-2621
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2621
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 3.4.9
> Environment: MINGW32_NT-6.1 on Windows 7 (e.g. git bash)
>Reporter: Amichai Rothman
>Assignee: Amichai Rothman
>
> The ZooKeeper scripts fail due to missing cygpath path conversion in a 
> MINGW32 environment, such as when running from git bash (installed by default 
> when installing Git for Windows).
> The fix is to add the line
> {quote}
> MINGW*) cygwin=true ;;
> {quote}
> near the bottom of the zkEnv.sh script, in the case statement that checks for 
> a cygwin environment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2621) ZooKeeper doesn't start on MINGW32 (Windows)

[Flavio Junqueira (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15608653#comment-15608653
 ] 

Flavio Junqueira commented on ZOOKEEPER-2621:
-

Thanks for reporting this issue. Could you please upload a patch? See the 
instructions to contribute here:

https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToContribute

> ZooKeeper doesn't start on MINGW32 (Windows)
> 
>
> Key: ZOOKEEPER-2621
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2621
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: scripts
>Affects Versions: 3.4.9
> Environment: MINGW32_NT-6.1 on Windows 7 (e.g. git bash)
>Reporter: Amichai Rothman
>Assignee: Amichai Rothman
>
> The ZooKeeper scripts fail due to missing cygpath path conversion in a 
> MINGW32 environment, such as when running from git bash (installed by default 
> when installing Git for Windows).
> The fix is to add the line
> {quote}
> MINGW*) cygwin=true ;;
> {quote}
> near the bottom of the zkEnv.sh script, in the case statement that checks for 
> a cygwin environment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-1652) zookeeper java client does a reverse dns lookup when connecting

[Flavio Junqueira (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15608599#comment-15608599
 ] 

Flavio Junqueira commented on ZOOKEEPER-1652:
-

Hello there, This issue duplicates ZOOKEEPER-1666, which has been fixed in 
3.4.6 and 3.5.0. 

> zookeeper java client does a reverse dns lookup when connecting
> ---
>
> Key: ZOOKEEPER-1652
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1652
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.5
>Reporter: Sean Bridges
>Assignee: Sean Bridges
>Priority: Critical
> Attachments: ZOOKEEPER-1652.patch
>
>
> When connecting to zookeeper, the client does a reverse dns lookup on the 
> hostname.  In our environment, the reverse dns lookup takes 5 seconds to 
> fail, causing zookeeper clients to connect slowly.
> The reverse dns lookup occurs in ClientCnx in the calls to adr.getHostName()
> {code}
> setName(getName().replaceAll("\\(.*\\)",
> "(" + addr.getHostName() + ":" + addr.getPort() + ")"));
> try {
> zooKeeperSaslClient = new 
> ZooKeeperSaslClient("zookeeper/"+addr.getHostName());
> } catch (LoginException e) {
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-1394) ClassNotFoundException on shutdown of client

[Flavio Junqueira (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15608591#comment-15608591
 ] 

Flavio Junqueira commented on ZOOKEEPER-1394:
-

The patch is trivial and it simply replaces the call to {{ZooTrace}} with 
{{LOG.debug}}, but I'm not convinced that this is the right way to fix this 
issue. In fact, I'm not even sure I fully understand the issue. Is there a way 
to reliably reproduce it?

I'm also thinking that {{ZooTrace}} is a bit abandoned, so we might want to 
make some fixes there.

> ClassNotFoundException on shutdown of client
> 
>
> Key: ZOOKEEPER-1394
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1394
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.2
> Environment: OS X 10.7 java version "1.6.0_29"
>Reporter: Herman Meerlo
>Assignee: wu wen
>Priority: Minor
> Attachments: ZOOKEEPER-1394.patch
>
>
> When close() is called on the ZooKeeper instance from a ContextListener 
> (contextDestroyed) there is no way to synchronize with the fact that the 
> EventThread and SendThread have actually finished their work. The problem 
> lies in the SendThread which makes a call to ZooTrace when it exits, but that 
> class has not been loaded yet. Because the ContextListener could not 
> synchronize with the death of the threads the classloader has already 
> disappeared, resulting in a ClassNotFoundException.
> My personal opinion is that the close() method should probably wait until the 
> event and send thread have actually died.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-1652) zookeeper java client does a reverse dns lookup when connecting

[Miguel Angel Fernandez Diaz (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15608585#comment-15608585
 ] 

Miguel Angel Fernandez Diaz commented on ZOOKEEPER-1652:


Hi,

I have a question about this issue, in which version is this resolved? Because 
there is no "Fixed version" in this ticket.

Thanks

> zookeeper java client does a reverse dns lookup when connecting
> ---
>
> Key: ZOOKEEPER-1652
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1652
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.5
>Reporter: Sean Bridges
>Assignee: Sean Bridges
>Priority: Critical
> Attachments: ZOOKEEPER-1652.patch
>
>
> When connecting to zookeeper, the client does a reverse dns lookup on the 
> hostname.  In our environment, the reverse dns lookup takes 5 seconds to 
> fail, causing zookeeper clients to connect slowly.
> The reverse dns lookup occurs in ClientCnx in the calls to adr.getHostName()
> {code}
> setName(getName().replaceAll("\\(.*\\)",
> "(" + addr.getHostName() + ":" + addr.getPort() + ")"));
> try {
> zooKeeperSaslClient = new 
> ZooKeeperSaslClient("zookeeper/"+addr.getHostName());
> } catch (LoginException e) {
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-1394) ClassNotFoundException on shutdown of client

[wu wen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

wu wen updated ZOOKEEPER-1394:
--
Attachment: ZOOKEEPER-1394.patch

> ClassNotFoundException on shutdown of client
> 
>
> Key: ZOOKEEPER-1394
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1394
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.2
> Environment: OS X 10.7 java version "1.6.0_29"
>Reporter: Herman Meerlo
>Assignee: wu wen
>Priority: Minor
> Attachments: ZOOKEEPER-1394.patch
>
>
> When close() is called on the ZooKeeper instance from a ContextListener 
> (contextDestroyed) there is no way to synchronize with the fact that the 
> EventThread and SendThread have actually finished their work. The problem 
> lies in the SendThread which makes a call to ZooTrace when it exits, but that 
> class has not been loaded yet. Because the ContextListener could not 
> synchronize with the death of the threads the classloader has already 
> disappeared, resulting in a ClassNotFoundException.
> My personal opinion is that the close() method should probably wait until the 
> event and send thread have actually died.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: ZOOKEEPER-1394 PreCommit Build #3503

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1394
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3503/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 34 lines...]
open files  (-n) 6
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 10240
virtual memory  (kbytes, -v) unlimited
file locks  (-x) unlimited
Buildfile: 
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/build.xml

check-for-findbugs:

findbugs.check:

forrest.check:

hudson-test-patch:
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Testing patch for ZOOKEEPER-1394.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] 
 [exec] ZOOKEEPER-1394 is not "Patch Available".  Exiting.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/patchprocess' 
and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/patchprocess' 
are the same file

BUILD SUCCESSFUL
Total time: 0 seconds
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
ERROR: No artifacts found that match the file pattern 
"build/test/findbugs/newPatchFindbugsWarnings.html,patchprocess/*.txt,patchprocess/*Warnings.xml,build/test/test-cppunit/*.txt,build/tmp/zk.log".
 Configuration error?
ERROR: ?build/test/findbugs/newPatchFindbugsWarnings.html? doesn?t match 
anything: even ?build? doesn?t exist
Build step 'Archive the artifacts' changed build result to FAILURE
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
ERROR: Step ?Publish JUnit test result report? failed: No test report files 
were found. Configuration error?
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-1394
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Created] (ZOOKEEPER-2622) ZooTrace.logQuorumPacket does nothing

[Flavio Junqueira (JIRA)]

Flavio Junqueira created ZOOKEEPER-2622:
---

 Summary: ZooTrace.logQuorumPacket does nothing
 Key: ZOOKEEPER-2622
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2622
 Project: ZooKeeper
  Issue Type: Bug
Reporter: Flavio Junqueira
Priority: Trivial
 Fix For: 3.5.3, 3.6.0


The method simply returns and there is some code commented out:

{code}
// if (isTraceEnabled(log, mask)) {
// logTraceMessage(LOG, mask, direction + " "
// + FollowerHandler.packetToString(qp));
// }
{code}

There are calls to this trace method, so I think we should fix it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-1394) ClassNotFoundException on shutdown of client

[wu wen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

wu wen updated ZOOKEEPER-1394:
--
Attachment: (was: ZOOKEEPER-1394.patch)

> ClassNotFoundException on shutdown of client
> 
>
> Key: ZOOKEEPER-1394
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1394
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.2
> Environment: OS X 10.7 java version "1.6.0_29"
>Reporter: Herman Meerlo
>Assignee: wu wen
>Priority: Minor
>
> When close() is called on the ZooKeeper instance from a ContextListener 
> (contextDestroyed) there is no way to synchronize with the fact that the 
> EventThread and SendThread have actually finished their work. The problem 
> lies in the SendThread which makes a call to ZooTrace when it exits, but that 
> class has not been loaded yet. Because the ContextListener could not 
> synchronize with the death of the threads the classloader has already 
> disappeared, resulting in a ClassNotFoundException.
> My personal opinion is that the close() method should probably wait until the 
> event and send thread have actually died.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-1394) ClassNotFoundException on shutdown of client

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15608345#comment-15608345
 ] 

Hadoop QA commented on ZOOKEEPER-1394:
--

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12835316/ZOOKEEPER-1394.patch
  against trunk revision f6349d16fcd5f04b560095417fd2a1813ac3e855.

+1 @author.  The patch does not contain any @author tags.

-1 tests included.  The patch doesn't appear to include any new or modified 
tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

+1 javadoc.  The javadoc tool did not generate any warning messages.

+1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

+1 findbugs.  The patch does not introduce any new Findbugs (version 2.0.3) 
warnings.

+1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

-1 core tests.  The patch failed core unit tests.

+1 contrib tests.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3502//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3502//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3502//console

This message is automatically generated.

> ClassNotFoundException on shutdown of client
> 
>
> Key: ZOOKEEPER-1394
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1394
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.2
> Environment: OS X 10.7 java version "1.6.0_29"
>Reporter: Herman Meerlo
>Assignee: wu wen
>Priority: Minor
> Attachments: ZOOKEEPER-1394.patch
>
>
> When close() is called on the ZooKeeper instance from a ContextListener 
> (contextDestroyed) there is no way to synchronize with the fact that the 
> EventThread and SendThread have actually finished their work. The problem 
> lies in the SendThread which makes a call to ZooTrace when it exits, but that 
> class has not been loaded yet. Because the ContextListener could not 
> synchronize with the death of the threads the classloader has already 
> disappeared, resulting in a ClassNotFoundException.
> My personal opinion is that the close() method should probably wait until the 
> event and send thread have actually died.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: ZOOKEEPER-1394 PreCommit Build #3502

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1394
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3502/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 415600 lines...]
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
(version 2.0.3) warnings.
 [exec] 
 [exec] +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.
 [exec] 
 [exec] -1 core tests.  The patch failed core unit tests.
 [exec] 
 [exec] +1 contrib tests.  The patch passed contrib unit tests.
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3502//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3502//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3502//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Comment added.
 [exec] 7e4d07ffa8fbd2e4001151c47b8881e3aa4cc98e logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/patchprocess' 
and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/patchprocess' 
are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/build.xml:1605: 
exec returned: 2

Total time: 13 minutes 29 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Compressed 550.89 KB of artifacts by 40.7% relative to #3501
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-1394
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  
org.apache.zookeeper.server.quorum.ReconfigRecoveryTest.testCurrentObserverIsParticipantInNewConfig

Error Message:
waiting for server 2 being up

Stack Trace:
junit.framework.AssertionFailedError: waiting for server 2 being up
at 
org.apache.zookeeper.server.quorum.ReconfigRecoveryTest.testCurrentObserverIsParticipantInNewConfig(ReconfigRecoveryTest.java:529)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)

ZooKeeper_branch35_jdk8 - Build # 280 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_jdk8/280/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 433276 lines...]
[junit] Tests run: 101, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
590.986 sec, Thread: 7, Class: org.apache.zookeeper.test.NioNettySuiteTest
[junit] 2016-10-26 12:16:14,208 [myid:127.0.0.1:27504] - INFO  
[main-SendThread(127.0.0.1:27504):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:27504. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-10-26 12:16:14,208 [myid:127.0.0.1:27504] - WARN  
[main-SendThread(127.0.0.1:27504):ClientCnxn$SendThread@1235] - Session 
0x201946a2c3c for server 127.0.0.1/127.0.0.1:27504, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2016-10-26 12:16:14,665 [myid:127.0.0.1:27380] - INFO  
[main-SendThread(127.0.0.1:27380):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:27380. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-10-26 12:16:14,666 [myid:127.0.0.1:27380] - WARN  
[main-SendThread(127.0.0.1:27380):ClientCnxn$SendThread@1235] - Session 
0x1019464df2f for server 127.0.0.1/127.0.0.1:27380, unexpected error, 
closing socket connection and attempting reconnect
[junit] java.net.ConnectException: Connection refused
[junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
[junit] at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
[junit] at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357)
[junit] at 
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214)
[junit] 2016-10-26 12:17:33,333 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 138089
[junit] 2016-10-26 12:17:33,334 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 55
[junit] 2016-10-26 12:17:33,334 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testManyChildWatchersAutoReset
[junit] 2016-10-26 12:17:33,334 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2016-10-26 12:17:33,335 [myid:] - INFO  [ProcessThread(sid:0 
cport:11225)::PrepRequestProcessor@647] - Processed session termination for 
sessionid: 0x1019462f217
[junit] 2016-10-26 12:17:33,359 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1019462f217
[junit] 2016-10-26 12:17:33,359 [myid:] - INFO  [main:ZooKeeper@1313] - 
Session: 0x1019462f217 closed
[junit] 2016-10-26 12:17:33,360 [myid:] - INFO  [ProcessThread(sid:0 
cport:11225)::PrepRequestProcessor@647] - Processed session termination for 
sessionid: 0x1019462f2170001
[junit] 2016-10-26 12:17:33,361 [myid:] - INFO  
[NIOWorkerThread-2:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port11225,name1=Connections,name2=127.0.0.1,name3=0x1019462f217]
[junit] 2016-10-26 12:17:33,361 [myid:] - INFO  
[NIOWorkerThread-2:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:48952 which had sessionid 0x1019462f217
[junit] 2016-10-26 12:17:33,392 [myid:] - INFO  
[NIOWorkerThread-3:MBeanRegistry@128] - Unregister MBean 
[org.apache.ZooKeeperService:name0=StandaloneServer_port11225,name1=Connections,name2=127.0.0.1,name3=0x1019462f2170001]
[junit] 2016-10-26 12:17:33,392 [myid:] - INFO  [main:ZooKeeper@1313] - 
Session: 0x1019462f2170001 closed
[junit] 2016-10-26 12:17:33,392 [myid:] - INFO  
[NIOWorkerThread-3:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:48993 which had sessionid 0x1019462f2170001
[junit] 2016-10-26 12:17:33,392 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1019462f2170001
[junit] 2016-10-26 12:17:33,392 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2016-10-26 12:17:33,393 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2016-10-26 12:17:33,395 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11225:NIOServerCnxnFactory$AcceptThread@219]
 - accept thread exitted run method
[junit] 2016-10-26 

[jira] [Commented] (ZOOKEEPER-2230) Connections fo ZooKeeper server becomes slow over time with native GSSAPI

[Deepesh Reja (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15608199#comment-15608199
 ] 

Deepesh Reja commented on ZOOKEEPER-2230:
-

Hi [~ekoontz]/[~mahadev],

>From ZOOKEEPER-938, I feel that you might be interested in this patch. Can you 
>please review and merge this?

Thanks,
Deepesh



> Connections fo ZooKeeper server becomes slow over time with native GSSAPI
> -
>
> Key: ZOOKEEPER-2230
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2230
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.6, 3.4.7, 3.4.8, 3.5.0
> Environment: OS: RHEL6
> Java: 1.8.0_40
> Configuration:
> java.env:
> {noformat}
> SERVER_JVMFLAGS="$SERVER_JVMFLAGS -Xmx5120m"
> SERVER_JVMFLAGS="$SERVER_JVMFLAGS 
> -Djava.security.auth.login.config=/local/apps/zookeeper-test1/conf/jaas-server.conf"
> SERVER_JVMFLAGS="$SERVER_JVMFLAGS -Dsun.security.jgss.native=true"
> {noformat}
> jaas-server.conf:
> {noformat}
> Server {
> com.sun.security.auth.module.Krb5LoginModule required
> useKeyTab=true
> isInitiator=false
> principal="zookeeper/@";
> };
> {noformat}
> Process environment:
> {noformat}
> KRB5_KTNAME=/local/apps/zookeeper-test1/conf/keytab
> ZOO_LOG_DIR=/local/apps/zookeeper-test1/log
> ZOOCFGDIR=/local/apps/zookeeper-test1/conf
> {noformat}
>Reporter: Deepesh Reja
>Assignee: Enis Soztutar
>  Labels: patch
> Fix For: 3.4.6, 3.4.7, 3.4.8, 3.5.2
>
> Attachments: ZOOKEEPER-2230.patch
>
>
> ZooKeeper server becomes slow over time when native GSSAPI is used. The 
> connection to the server starts taking upto 10 seconds.
> This is happening with ZooKeeper-3.4.6 and is fairly reproducible.
> Debug logs:
> {noformat}
> 2015-07-02 00:58:49,318 [myid:] - INFO  
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:42405:NIOServerCnxnFactory@197] - 
> Accepted socket connection from /:47942
> 2015-07-02 00:58:49,318 [myid:] - DEBUG 
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:42405:ZooKeeperSaslServer@78] - 
> serviceHostname is ''
> 2015-07-02 00:58:49,318 [myid:] - DEBUG 
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:42405:ZooKeeperSaslServer@79] - 
> servicePrincipalName is 'zookeeper'
> 2015-07-02 00:58:49,318 [myid:] - DEBUG 
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:42405:ZooKeeperSaslServer@80] - SASL 
> mechanism(mech) is 'GSSAPI'
> 2015-07-02 00:58:49,324 [myid:] - DEBUG 
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:42405:ZooKeeperSaslServer@106] - Added 
> private credential to subject: [GSSCredential: 
> zookeeper@ 1.2.840.113554.1.2.2 Accept [class 
> sun.security.jgss.wrapper.GSSCredElement]]
> 2015-07-02 00:58:59,441 [myid:] - DEBUG 
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:42405:ZooKeeperServer@810] - Session 
> establishment request from client /:47942 client's lastZxid is 0x0
> 2015-07-02 00:58:59,441 [myid:] - INFO  
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:42405:ZooKeeperServer@868] - Client 
> attempting to establish new session at /:47942
> 2015-07-02 00:58:59,448 [myid:] - DEBUG 
> [SyncThread:0:FinalRequestProcessor@88] - Processing request:: 
> sessionid:0x14e486028785c81 type:createSession cxid:0x0 zxid:0x110e79 
> txntype:-10 reqpath:n/a
> 2015-07-02 00:58:59,448 [myid:] - DEBUG 
> [SyncThread:0:FinalRequestProcessor@160] - sessionid:0x14e486028785c81 
> type:createSession cxid:0x0 zxid:0x110e79 txntype:-10 reqpath:n/a
> 2015-07-02 00:58:59,448 [myid:] - INFO  [SyncThread:0:ZooKeeperServer@617] - 
> Established session 0x14e486028785c81 with negotiated timeout 1 for 
> client /:47942
> 2015-07-02 00:58:59,452 [myid:] - DEBUG 
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:42405:ZooKeeperServer@949] - Responding 
> to client SASL token.
> 2015-07-02 00:58:59,452 [myid:] - DEBUG 
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:42405:ZooKeeperServer@953] - Size of 
> client SASL token: 706
> 2015-07-02 00:58:59,460 [myid:] - DEBUG 
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:42405:ZooKeeperServer@984] - Size of 
> server SASL response: 161
> 2015-07-02 00:58:59,462 [myid:] - DEBUG 
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:42405:ZooKeeperServer@949] - Responding 
> to client SASL token.
> 2015-07-02 00:58:59,462 [myid:] - DEBUG 
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:42405:ZooKeeperServer@953] - Size of 
> client SASL token: 0
> 2015-07-02 00:58:59,462 [myid:] - DEBUG 
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:42405:ZooKeeperServer@984] - Size of 
> server SASL response: 32
> 2015-07-02 00:58:59,463 [myid:] - DEBUG 
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:42405:ZooKeeperServer@949] - Responding 
> to client SASL token.
> 2015-07-02 00:58:59,463 [myid:] - DEBUG 
> [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:42405:ZooKeeperServer@953] - Size of 
> client SASL token: 32
> 2015-07-02 00:58:59,464 [myid:] - INFO  
> 

[jira] [Updated] (ZOOKEEPER-1394) ClassNotFoundException on shutdown of client

[Flavio Junqueira (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flavio Junqueira updated ZOOKEEPER-1394:

Assignee: wu wen

> ClassNotFoundException on shutdown of client
> 
>
> Key: ZOOKEEPER-1394
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1394
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.4.2
> Environment: OS X 10.7 java version "1.6.0_29"
>Reporter: Herman Meerlo
>Assignee: wu wen
>Priority: Minor
>
> When close() is called on the ZooKeeper instance from a ContextListener 
> (contextDestroyed) there is no way to synchronize with the fact that the 
> EventThread and SendThread have actually finished their work. The problem 
> lies in the SendThread which makes a call to ZooTrace when it exits, but that 
> class has not been loaded yet. Because the ContextListener could not 
> synchronize with the death of the threads the classloader has already 
> disappeared, resulting in a ClassNotFoundException.
> My personal opinion is that the close() method should probably wait until the 
> event and send thread have actually died.



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

[Rakesh Kumar Singh (JIRA)]

 [ 
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

[Rakesh Kumar Singh (JIRA)]

 [ 
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

[Rakesh Kumar Singh (JIRA)]

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

Success: ZOOKEEPER-2556 PreCommit Build #3501

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2556
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3501/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 417805 lines...]
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +1 tests included.  The patch appears to include 6 new or 
modified tests.
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
(version 2.0.3) warnings.
 [exec] 
 [exec] +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.
 [exec] 
 [exec] +1 core tests.  The patch passed core unit tests.
 [exec] 
 [exec] +1 contrib tests.  The patch passed contrib unit tests.
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3501//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3501//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3501//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Comment added.
 [exec] f3384ed08ae302d0b33fe9ab25e17500fd610933 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/patchprocess' 
and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/patchprocess' 
are the same file

BUILD SUCCESSFUL
Total time: 19 minutes 17 seconds
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2556
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Success
Sending email for trigger: Success
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

ZooKeeper-trunk-solaris - Build # 1362 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk-solaris/1362/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 437691 lines...]
[junit] 2016-10-26 08:35:39,991 [myid:] - INFO  [main:ClientBase@386] - 
CREATING server instance 127.0.0.1:11222
[junit] 2016-10-26 08:35:39,992 [myid:] - INFO  
[main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s 
sessionless connection timeout, 2 selector thread(s), 16 worker threads, and 64 
kB direct buffers.
[junit] 2016-10-26 08:35:39,993 [myid:] - INFO  
[main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222
[junit] 2016-10-26 08:35:39,993 [myid:] - INFO  [main:ClientBase@361] - 
STARTING server instance 127.0.0.1:11222
[junit] 2016-10-26 08:35:39,994 [myid:] - INFO  [main:ZooKeeperServer@889] 
- minSessionTimeout set to 6000
[junit] 2016-10-26 08:35:39,994 [myid:] - INFO  [main:ZooKeeperServer@898] 
- maxSessionTimeout set to 6
[junit] 2016-10-26 08:35:39,994 [myid:] - INFO  [main:ZooKeeperServer@159] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test8081657793356341810.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test8081657793356341810.junit.dir/version-2
[junit] 2016-10-26 08:35:39,995 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test8081657793356341810.junit.dir/version-2/snapshot.b
[junit] 2016-10-26 08:35:39,997 [myid:] - INFO  [main:FileTxnSnapLog@306] - 
Snapshotting: 0xb to 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/build/test/tmp/test8081657793356341810.junit.dir/version-2/snapshot.b
[junit] 2016-10-26 08:35:39,999 [myid:] - ERROR [main:ZooKeeperServer@501] 
- ZKShutdownHandler is not registered, so ZooKeeper server won't take any 
action on ERROR or SHUTDOWN server state changes
[junit] 2016-10-26 08:35:39,999 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-10-26 08:35:39,999 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:32861
[junit] 2016-10-26 08:35:40,000 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:32861
[junit] 2016-10-26 08:35:40,000 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2016-10-26 08:35:40,001 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:32861 (no session established for client)
[junit] 2016-10-26 08:35:40,001 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-10-26 08:35:40,007 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2016-10-26 08:35:40,007 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2016-10-26 08:35:40,007 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2016-10-26 08:35:40,008 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2016-10-26 08:35:40,008 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17666
[junit] 2016-10-26 08:35:40,008 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24
[junit] 2016-10-26 08:35:40,008 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2016-10-26 08:35:40,008 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2016-10-26 08:35:40,083 [myid:] - INFO  [main:ZooKeeper@1315] - 
Session: 0x1247d1c1da5 closed
[junit] 2016-10-26 08:35:40,083 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1247d1c1da5
[junit] 2016-10-26 08:35:40,084 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2016-10-26 08:35:40,085 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2016-10-26 08:35:40,085 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@219]
 - accept thread exitted run method
[junit] 2016-10-26 08:35:40,086 [myid:] - INFO  

Success: ZOOKEEPER-2556 PreCommit Build #3500

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2556
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3500/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 409874 lines...]
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +1 tests included.  The patch appears to include 6 new or 
modified tests.
 [exec] 
 [exec] +1 javadoc.  The javadoc tool did not generate any warning 
messages.
 [exec] 
 [exec] +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
 [exec] 
 [exec] +1 findbugs.  The patch does not introduce any new Findbugs 
(version 2.0.3) warnings.
 [exec] 
 [exec] +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.
 [exec] 
 [exec] +1 core tests.  The patch passed core unit tests.
 [exec] 
 [exec] +1 contrib tests.  The patch passed contrib unit tests.
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3500//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3500//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3500//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Comment added.
 [exec] 41f6f34e258de5178a22b0b1ed6621d8b7ce5216 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/patchprocess' 
and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/patchprocess' 
are the same file

BUILD SUCCESSFUL
Total time: 18 minutes 16 seconds
Archiving artifacts
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Recording test results
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
[description-setter] Description set: ZOOKEEPER-2556
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Email was triggered for: Success
Sending email for trigger: Success
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7
Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7



###
## FAILED TESTS (if any) 
##
All tests passed

[jira] [Commented] (ZOOKEEPER-2556) peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime

[Alexander Shraer (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15607790#comment-15607790
 ] 

Alexander Shraer commented on ZOOKEEPER-2556:
-

looks good, but I think the check that peerType is not in cfg shouldn't be in 
the inner loop.

> 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] [Updated] (ZOOKEEPER-2556) peerType remains as "observer" in zoo.cfg even though we change the node from observer to participant runtime

[Rakesh Kumar Singh (JIRA)]

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