ZooKeeper_branch34_jdk8 - Build # 940 - Failure
See https://builds.apache.org/job/ZooKeeper_branch34_jdk8/940/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 31.95 MB...] [junit] 2017-03-30 23:06:32,896 [myid:] - INFO [ProcessThread(sid:0 cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop! [junit] 2017-03-30 23:06:32,896 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited! [junit] 2017-03-30 23:06:32,897 [myid:] - INFO [main:FinalRequestProcessor@402] - shutdown of request processor complete [junit] 2017-03-30 23:06:32,897 [myid:] - INFO [main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221 [junit] 2017-03-30 23:06:32,898 [myid:] - INFO [main:JMXEnv@147] - ensureOnly:[] [junit] 2017-03-30 23:06:32,899 [myid:] - INFO [main:ClientBase@445] - STARTING server [junit] 2017-03-30 23:06:32,899 [myid:] - INFO [main:ClientBase@366] - CREATING server instance 127.0.0.1:11221 [junit] 2017-03-30 23:06:32,900 [myid:] - INFO [main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2017-03-30 23:06:32,900 [myid:] - INFO [main:ClientBase@341] - STARTING server instance 127.0.0.1:11221 [junit] 2017-03-30 23:06:32,901 [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/test5908498345645134126.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/build/test/tmp/test5908498345645134126.junit.dir/version-2 [junit] 2017-03-30 23:06:32,903 [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] 2017-03-30 23:06:32,904 [myid:] - INFO [main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221 [junit] 2017-03-30 23:06:32,904 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - Accepted socket connection from /127.0.0.1:39247 [junit] 2017-03-30 23:06:32,904 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@883] - Processing stat command from /127.0.0.1:39247 [junit] 2017-03-30 23:06:32,905 [myid:] - INFO [Thread-4:NIOServerCnxn$StatCommand@674] - Stat command output [junit] 2017-03-30 23:06:32,905 [myid:] - INFO [Thread-4:NIOServerCnxn@1044] - Closed socket connection for client /127.0.0.1:39247 (no session established for client) [junit] 2017-03-30 23:06:32,906 [myid:] - INFO [main:JMXEnv@230] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2017-03-30 23:06:32,907 [myid:] - INFO [main:JMXEnv@247] - expect:InMemoryDataTree [junit] 2017-03-30 23:06:32,908 [myid:] - INFO [main:JMXEnv@251] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree [junit] 2017-03-30 23:06:32,908 [myid:] - INFO [main:JMXEnv@247] - expect:StandaloneServer_port [junit] 2017-03-30 23:06:32,908 [myid:] - INFO [main:JMXEnv@251] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11221 [junit] 2017-03-30 23:06:32,908 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 35528 [junit] 2017-03-30 23:06:32,909 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20 [junit] 2017-03-30 23:06:32,909 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota [junit] 2017-03-30 23:06:32,909 [myid:] - INFO [main:ClientBase@522] - tearDown starting [junit] 2017-03-30 23:06:32,981 [myid:] - INFO [main:ZooKeeper@684] - Session: 0x15b21786ed3 closed [junit] 2017-03-30 23:06:32,981 [myid:] - INFO [main:ClientBase@492] - STOPPING server [junit] 2017-03-30 23:06:32,981 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for session: 0x15b21786ed3 [junit] 2017-03-30 23:06:32,981 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - NIOServerCnxn factory exited run method [junit] 2017-03-30 23:06:32,982 [myid:] - INFO [main:ZooKeeperServer@505] - shutting down [junit] 2017-03-30 23:06:32,982 [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] 2017-03-30 23:06:32,982 [myid:] - INFO [main:SessionTrackerImpl@225] - Shutting down [junit] 2017-03-30 23:06:32,982 [myid:] - INFO [main:PrepRequestProcessor@764] - Shutting down [junit] 2017-03-30 23:06:32,982 [myid:] - INFO [main:SyncRequestProcessor@208] - Shutting down [junit] 2017-03-30 23:06:32,982
[jira] [Comment Edited] (ZOOKEEPER-900) FLE implementation should be improved to use non-blocking sockets
[ https://issues.apache.org/jira/browse/ZOOKEEPER-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15950030#comment-15950030 ] Michael Han edited comment on ZOOKEEPER-900 at 3/30/17 11:02 PM: - I think Martin might move on to something else - it sounds OK to reassign the issue to [~atris]. [~phunt] Do you mind help add [~atris] to JIRA contributor list? was (Author: hanm): I think Martin might move on to something else - it sounds OK to reassign the issue to [~atris]. [~phunt] Do you might help add [~atris] to JIRA contributor list? > FLE implementation should be improved to use non-blocking sockets > - > > Key: ZOOKEEPER-900 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-900 > Project: ZooKeeper > Issue Type: Bug >Reporter: Vishal Kher >Assignee: Martin Kuchta >Priority: Critical > Fix For: 3.5.4, 3.6.0 > > Attachments: ZOOKEEPER-900-part2.patch, ZOOKEEPER-900.patch, > ZOOKEEPER-900.patch1, ZOOKEEPER-900.patch2 > > > From earlier email exchanges: > 1. Blocking connects and accepts: > a) The first problem is in manager.toSend(). This invokes connectOne(), which > does a blocking connect. While testing, I changed the code so that > connectOne() starts a new thread called AsyncConnct(). AsyncConnect.run() > does a socketChannel.connect(). After starting AsyncConnect, connectOne > starts a timer. connectOne continues with normal operations if the connection > is established before the timer expires, otherwise, when the timer expires it > interrupts AsyncConnect() thread and returns. In this way, I can have an > upper bound on the amount of time we need to wait for connect to succeed. Of > course, this was a quick fix for my testing. Ideally, we should use Selector > to do non-blocking connects/accepts. I am planning to do that later once we > at least have a quick fix for the problem and consensus from others for the > real fix (this problem is big blocker for us). Note that it is OK to do > blocking IO in SenderWorker and RecvWorker threads since they block IO to the > respective peer. > b) The blocking IO problem is not just restricted to connectOne(), but also > in receiveConnection(). The Listener thread calls receiveConnection() for > each incoming connection request. receiveConnection does blocking IO to get > peer's info (s.read(msgBuffer)). Worse, it invokes connectOne() back to the > peer that had sent the connection request. All of this is happening from the > Listener. In short, if a peer fails after initiating a connection, the > Listener thread won't be able to accept connections from other peers, because > it would be stuck in read() or connetOne(). Also the code has an inherent > cycle. initiateConnection() and receiveConnection() will have to be very > carefully synchronized otherwise, we could run into deadlocks. This code is > going to be difficult to maintain/modify. > Also see: https://issues.apache.org/jira/browse/ZOOKEEPER-822 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ZOOKEEPER-900) FLE implementation should be improved to use non-blocking sockets
[ https://issues.apache.org/jira/browse/ZOOKEEPER-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15950030#comment-15950030 ] Michael Han commented on ZOOKEEPER-900: --- I think Martin might move on to something else - it sounds OK to reassign the issue to [~atris]. [~phunt] Do you might help add [~atris] to JIRA contributor list? > FLE implementation should be improved to use non-blocking sockets > - > > Key: ZOOKEEPER-900 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-900 > Project: ZooKeeper > Issue Type: Bug >Reporter: Vishal Kher >Assignee: Martin Kuchta >Priority: Critical > Fix For: 3.5.4, 3.6.0 > > Attachments: ZOOKEEPER-900-part2.patch, ZOOKEEPER-900.patch, > ZOOKEEPER-900.patch1, ZOOKEEPER-900.patch2 > > > From earlier email exchanges: > 1. Blocking connects and accepts: > a) The first problem is in manager.toSend(). This invokes connectOne(), which > does a blocking connect. While testing, I changed the code so that > connectOne() starts a new thread called AsyncConnct(). AsyncConnect.run() > does a socketChannel.connect(). After starting AsyncConnect, connectOne > starts a timer. connectOne continues with normal operations if the connection > is established before the timer expires, otherwise, when the timer expires it > interrupts AsyncConnect() thread and returns. In this way, I can have an > upper bound on the amount of time we need to wait for connect to succeed. Of > course, this was a quick fix for my testing. Ideally, we should use Selector > to do non-blocking connects/accepts. I am planning to do that later once we > at least have a quick fix for the problem and consensus from others for the > real fix (this problem is big blocker for us). Note that it is OK to do > blocking IO in SenderWorker and RecvWorker threads since they block IO to the > respective peer. > b) The blocking IO problem is not just restricted to connectOne(), but also > in receiveConnection(). The Listener thread calls receiveConnection() for > each incoming connection request. receiveConnection does blocking IO to get > peer's info (s.read(msgBuffer)). Worse, it invokes connectOne() back to the > peer that had sent the connection request. All of this is happening from the > Listener. In short, if a peer fails after initiating a connection, the > Listener thread won't be able to accept connections from other peers, because > it would be stuck in read() or connetOne(). Also the code has an inherent > cycle. initiateConnection() and receiveConnection() will have to be very > carefully synchronized otherwise, we could run into deadlocks. This code is > going to be difficult to maintain/modify. > Also see: https://issues.apache.org/jira/browse/ZOOKEEPER-822 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: Patch for ZOOKEEPER-2184 feedback
HI Powell, Have you looked at the existing PR ( https://github.com/apache/zookeeper/pull/150) for ZOOKEEPER-2184? I think that's what community is working on, and it's close to get merged, so probably worth to adjust your work on top of that issue? On Wed, Mar 29, 2017 at 9:25 PM, powell molletiwrote: > Hi, > > > I was wondering if anyone has cycles to look at the PR I have for > ZOOKEEPER-2184: Resolve address only on demand ( > https://github.com/apache/zookeeper/pull/199 ). > > Let me know if I am heading in the wrong direction any pointers will help > me to use these changes or drop them from a different PR I have. > > thanks > Powell. > -- Cheers Michael.
[GitHub] zookeeper issue #210: Fix typo
Github user eribeiro commented on the issue: https://github.com/apache/zookeeper/pull/210 +1 to what @afine wrote. Plus, target your PR to **branch-3.4** and then we can cherry-pick it into branch-3.5 and master after applying it to branch-3.4 --- 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: Zookeeper build on Mac
"ant clean jar" works for me on my mac (jdk 1.8) more details on the how to contribute page: https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToContribute Patrick On Wed, Mar 29, 2017 at 4:34 PM, cst labswrote: > I can't seem to find any instructions to build zookeeper on Mac. Is there a > link or a pointer to the set of build instructions? >
[jira] [Created] (ZOOKEEPER-2742) Few test cases of org.apache.zookeeper.ZooKeeperTest fails in Windows.
Abhishek Kumar created ZOOKEEPER-2742: - Summary: Few test cases of org.apache.zookeeper.ZooKeeperTest fails in Windows. Key: ZOOKEEPER-2742 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2742 Project: ZooKeeper Issue Type: Test Components: tests Environment: Windows Reporter: Abhishek Kumar Priority: Trivial Following test cases fail in Windows environment: 1. org.apache.zookeeper.ZooKeeperTest.testLsrRootCommand() 2. org.apache.zookeeper.ZooKeeperTest.testLsrCommand() It seems that failure is related to use of "\n" (System dependent new line char)in org.apache.zookeeper.ZooKeeperTest.runCommandExpect(CliCommand, List) .. .. String result = byteStream.toString(); assertTrue(result, result.contains( StringUtils.joinStrings(expectedResults, "\n"))); .. .. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
ZooKeeper_branch34_openjdk7 - Build # 1449 - Failure
See https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1449/ ### ## LAST 60 LINES OF THE CONSOLE ### Started by timer [EnvInject] - Loading node environment variables. Building remotely on ubuntu-2 (ubuntu) in workspace /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7 FATAL: java.io.IOException: Remote call on ubuntu-2 failed hudson.remoting.RemotingSystemException: java.io.IOException: Remote call on ubuntu-2 failed at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:272) at com.sun.proxy.$Proxy96.hasGitRepo(Unknown Source) at org.jenkinsci.plugins.gitclient.RemoteGitImpl.hasGitRepo(RemoteGitImpl.java:280) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1046) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1101) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1728) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Caused by: java.io.IOException: Remote call on ubuntu-2 failed at hudson.remoting.Channel.call(Channel.java:830) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256) ... 13 more Caused by: java.lang.OutOfMemoryError: Java heap space Recording test results ERROR: Step ?Publish JUnit test result report? failed: Test reports were found but none of them are new. Did tests run? For example, /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7/build/test/logs/TEST-org.apache.jute.BinaryInputArchiveTest.xml is 12 days old Email was triggered for: Failure - Any Sending email for trigger: Failure - Any ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Commented] (ZOOKEEPER-1061) Zookeeper stop fails if start called twice
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15949160#comment-15949160 ] mark kozikowski commented on ZOOKEEPER-1061: I believe there is a small error in the patch for the zookeeper start script. The section in question relates to 'start' +echo FAILED TO WRITE PID +exit 1 I would like to see the 'just started' zookeeper stopped if the pid file failed to write Otherwise, we lose the ability to stop it later, and we might have start issues again if we try to restart it. Mark > Zookeeper stop fails if start called twice > -- > > Key: ZOOKEEPER-1061 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1061 > Project: ZooKeeper > Issue Type: Bug > Components: scripts >Affects Versions: 3.3.2 >Reporter: Ted Dunning >Assignee: Ted Dunning > Fix For: 3.4.0 > > Attachments: ZOOKEEPER-1061.patch > > > The zkServer.sh script doesn't check properly to see if a previously started > server is still running. If you call start twice, the second invocation > will over-write the PID file with a process that then fails due to port > occupancy. > This means that stop will subsequently fail. > Here is a reference that describes how init scripts should normally work: > http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
ZooKeeper-trunk-jdk8 - Build # 998 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/998/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 65.33 MB...] [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] 2017-03-30 11:58:57,927 [myid:127.0.0.1:11345] - INFO [main-SendThread(127.0.0.1:11345):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:11345. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-03-30 11:58:57,927 [myid:127.0.0.1:11345] - WARN [main-SendThread(127.0.0.1:11345):ClientCnxn$SendThread@1235] - Session 0x100e52fa699 for server 127.0.0.1/127.0.0.1:11345, 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] 2017-03-30 11:58:58,282 [myid:] - INFO [SessionTracker:SessionTrackerImpl@158] - SessionTrackerImpl exited loop! [junit] 2017-03-30 11:58:58,782 [myid:] - INFO [ProcessThread(sid:0 cport:11468)::PrepRequestProcessor@617] - Processed session termination for sessionid: 0x100e5330d85 [junit] 2017-03-30 11:58:58,798 [myid:] - INFO [SyncThread:0:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port11468,name1=Connections,name2=127.0.0.1,name3=0x100e5330d85] [junit] 2017-03-30 11:58:58,799 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for session: 0x100e5330d85 [junit] 2017-03-30 11:58:58,798 [myid:] - INFO [main:ZooKeeper@1324] - Session: 0x100e5330d85 closed [junit] 2017-03-30 11:58:58,799 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 144264 [junit] 2017-03-30 11:58:58,799 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 1643 [junit] 2017-03-30 11:58:58,799 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testWatcherAutoResetWithLocal [junit] 2017-03-30 11:58:58,799 [myid:] - INFO [main:ClientBase@558] - tearDown starting [junit] 2017-03-30 11:58:58,800 [myid:] - INFO [main:ClientBase@528] - STOPPING server [junit] 2017-03-30 11:58:58,800 [myid:] - INFO [main:NettyServerCnxnFactory@464] - shutdown called 0.0.0.0/0.0.0.0:11468 [junit] 2017-03-30 11:58:58,801 [myid:] - INFO [main:ZooKeeperServer@542] - shutting down [junit] 2017-03-30 11:58:58,802 [myid:] - ERROR [main:ZooKeeperServer@506] - ZKShutdownHandler is not registered, so ZooKeeper server won't take any action on ERROR or SHUTDOWN server state changes [junit] 2017-03-30 11:58:58,802 [myid:] - INFO [main:SessionTrackerImpl@232] - Shutting down [junit] 2017-03-30 11:58:58,802 [myid:] - INFO [main:PrepRequestProcessor@1008] - Shutting down [junit] 2017-03-30 11:58:58,802 [myid:] - INFO [main:SyncRequestProcessor@191] - Shutting down [junit] 2017-03-30 11:58:58,802 [myid:] - INFO [ProcessThread(sid:0 cport:11468)::PrepRequestProcessor@157] - PrepRequestProcessor exited loop! [junit] 2017-03-30 11:58:58,804 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited! [junit] 2017-03-30 11:58:58,804 [myid:] - INFO [main:FinalRequestProcessor@481] - shutdown of request processor complete [junit] 2017-03-30 11:58:58,805 [myid:] - INFO [main:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port11468,name1=InMemoryDataTree] [junit] 2017-03-30 11:58:58,805 [myid:] - INFO [main:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port11468] [junit] 2017-03-30 11:58:58,805 [myid:] - INFO [main:FourLetterWordMain@85] - connecting to 127.0.0.1 11468 [junit] 2017-03-30 11:58:58,806 [myid:] - INFO [main:JMXEnv@146] - ensureOnly:[] [junit] 2017-03-30 11:58:58,818 [myid:] - INFO [main:ClientBase@583] - fdcount after test is: 4849 at start it was 4854 [junit] 2017-03-30 11:58:58,818 [myid:] - INFO [main:ZKTestCase$1@68] - SUCCEEDED testWatcherAutoResetWithLocal [junit] 2017-03-30 11:58:58,818 [myid:] - INFO