[jira] [Created] (ZOOKEEPER-2250) Support client connections using a SOCKS proxy
David Phillips created ZOOKEEPER-2250: - Summary: Support client connections using a SOCKS proxy Key: ZOOKEEPER-2250 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2250 Project: ZooKeeper Issue Type: New Feature Components: java client Reporter: David Phillips Connecting to ZooKeeper via a SOCKS proxy is often useful for debugging systems over an SSH dynamic port forward. It is possible to do this today with some hacking by setting "zookeeper.clientCnxnSocket", but that is difficult because ClientCnxnSocket is package-private and is quite low-level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ZOOKEEPER-1907) Improve Thread handling
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hongchao Deng resolved ZOOKEEPER-1907.
--
Resolution: Fixed
> Improve Thread handling
> ---
>
> Key: ZOOKEEPER-1907
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1907
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
>Affects Versions: 3.5.0
>Reporter: Rakesh R
>Assignee: Rakesh R
> Fix For: 3.4.7, 3.5.1, 3.6.0
>
> Attachments: ZOOKEEPER-1907-br-3-4.patch, ZOOKEEPER-1907.patch,
> ZOOKEEPER-1907.patch, ZOOKEEPER-1907.patch, ZOOKEEPER-1907.patch,
> ZOOKEEPER-1907.patch, ZOOKEEPER-1907.patch, ZOOKEEPER-1907.patch,
> ZOOKEEPER-1907.patch, ZOOKEEPER-1907.patch, ZOOKEEPER-1907.patch,
> ZOOKEEPER-1907.patch, ZOOKEEPER-1907.patch, ZOOKEEPER-1907.patch
>
>
> Server has many critical threads running and co-ordinating each other like
> RequestProcessor chains et. When going through each threads, most of them
> having the similar structure like:
> {code}
> public void run() {
> try {
> while(running)
>// processing logic
> }
> } catch (InterruptedException e) {
> LOG.error("Unexpected interruption", e);
> } catch (Exception e) {
> LOG.error("Unexpected exception", e);
> }
> LOG.info("...exited loop!");
> }
> {code}
> From the design I could see, there could be a chance of silently leaving the
> thread by swallowing the exception. If this happens in the production, the
> server would get hanged forever and would not be able to deliver its role.
> Now its hard for the management tool to detect this.
> The idea of this JIRA is to discuss and imprv.
> Reference: [Community discussion
> thread|http://mail-archives.apache.org/mod_mbox/zookeeper-user/201403.mbox/%3cc2496325850aa74c92aaf83aa9662d26458a1...@szxeml561-mbx.china.huawei.com%3E]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1907) Improve Thread handling
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700205#comment-14700205
]
Hongchao Deng commented on ZOOKEEPER-1907:
--
Committed to branch-3.4:
https://github.com/apache/zookeeper/commit/91f579e40755de870ed9123c8fd55925517d9aa6
Thanks [~rakeshr]!
> Improve Thread handling
> ---
>
> Key: ZOOKEEPER-1907
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1907
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
>Affects Versions: 3.5.0
>Reporter: Rakesh R
>Assignee: Rakesh R
> Fix For: 3.4.7, 3.5.1, 3.6.0
>
> Attachments: ZOOKEEPER-1907-br-3-4.patch, ZOOKEEPER-1907.patch,
> ZOOKEEPER-1907.patch, ZOOKEEPER-1907.patch, ZOOKEEPER-1907.patch,
> ZOOKEEPER-1907.patch, ZOOKEEPER-1907.patch, ZOOKEEPER-1907.patch,
> ZOOKEEPER-1907.patch, ZOOKEEPER-1907.patch, ZOOKEEPER-1907.patch,
> ZOOKEEPER-1907.patch, ZOOKEEPER-1907.patch, ZOOKEEPER-1907.patch
>
>
> Server has many critical threads running and co-ordinating each other like
> RequestProcessor chains et. When going through each threads, most of them
> having the similar structure like:
> {code}
> public void run() {
> try {
> while(running)
>// processing logic
> }
> } catch (InterruptedException e) {
> LOG.error("Unexpected interruption", e);
> } catch (Exception e) {
> LOG.error("Unexpected exception", e);
> }
> LOG.info("...exited loop!");
> }
> {code}
> From the design I could see, there could be a chance of silently leaving the
> thread by swallowing the exception. If this happens in the production, the
> server would get hanged forever and would not be able to deliver its role.
> Now its hard for the management tool to detect this.
> The idea of this JIRA is to discuss and imprv.
> Reference: [Community discussion
> thread|http://mail-archives.apache.org/mod_mbox/zookeeper-user/201403.mbox/%3cc2496325850aa74c92aaf83aa9662d26458a1...@szxeml561-mbx.china.huawei.com%3E]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-1029) C client bug in zookeeper_init (if bad hostname is given)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700149#comment-14700149 ] Steven Schlansker commented on ZOOKEEPER-1029: -- I am raising the priority of this issue to 'Blocker' as it 1) is a complete crash of the ZK client 2) affects multiple users 3) affects production stability 4) has been open for a very long time. Hopefully it can be considered for the next releases of the 3.4.x and 3.5.x series? > C client bug in zookeeper_init (if bad hostname is given) > - > > Key: ZOOKEEPER-1029 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1029 > Project: ZooKeeper > Issue Type: Bug > Components: c client >Affects Versions: 3.3.2, 3.4.6, 3.5.0 >Reporter: Dheeraj Agrawal >Priority: Blocker > Fix For: 3.4.7, 3.5.2 > > > If you give invalid hostname to zookeeper_init method, it's not able to > resolve it, and it tries to do the cleanup (free buffer/completion lists/etc) > . The adaptor_init() is not called for this code path, so the lock,cond > variables (for adaptor, completion lists) are not initialized. > As part of the cleanup it's trying to clean up some buffers and acquires > locks and unlocks (where the locks have not yet been initialized, so > unlocking fails) > lock_completion_list(&zh->sent_requests); - pthread_mutex/cond not > initialized > tmp_list = zh->sent_requests; > zh->sent_requests.head = 0; > zh->sent_requests.last = 0; > unlock_completion_list(&zh->sent_requests); trying to broadcast here > on uninitialized cond > It should do error checking to see if locking succeeds before unlocking it. > If Locking fails, then appropriate error handling has to be done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-1029) C client bug in zookeeper_init (if bad hostname is given)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Schlansker updated ZOOKEEPER-1029: - Priority: Blocker (was: Major) > C client bug in zookeeper_init (if bad hostname is given) > - > > Key: ZOOKEEPER-1029 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1029 > Project: ZooKeeper > Issue Type: Bug > Components: c client >Affects Versions: 3.3.2, 3.4.6, 3.5.0 >Reporter: Dheeraj Agrawal >Priority: Blocker > Fix For: 3.4.7, 3.5.2 > > > If you give invalid hostname to zookeeper_init method, it's not able to > resolve it, and it tries to do the cleanup (free buffer/completion lists/etc) > . The adaptor_init() is not called for this code path, so the lock,cond > variables (for adaptor, completion lists) are not initialized. > As part of the cleanup it's trying to clean up some buffers and acquires > locks and unlocks (where the locks have not yet been initialized, so > unlocking fails) > lock_completion_list(&zh->sent_requests); - pthread_mutex/cond not > initialized > tmp_list = zh->sent_requests; > zh->sent_requests.head = 0; > zh->sent_requests.last = 0; > unlock_completion_list(&zh->sent_requests); trying to broadcast here > on uninitialized cond > It should do error checking to see if locking succeeds before unlocking it. > If Locking fails, then appropriate error handling has to be done. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
ZooKeeper-trunk-jdk8 - Build # 476 - Failure
See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/476/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 367621 lines...] [junit] 2015-08-17 17:11:02,858 [myid:] - INFO [main:FourLetterWordMain@84] - connecting to 127.0.0.1 11222 [junit] 2015-08-17 17:11:02,859 [myid:] - INFO [main:JMXEnv@142] - ensureOnly:[] [junit] 2015-08-17 17:11:02,860 [myid:] - INFO [main:ClientBase@460] - STARTING server [junit] 2015-08-17 17:11:02,861 [myid:] - INFO [main:ClientBase@380] - CREATING server instance 127.0.0.1:11222 [junit] 2015-08-17 17:11:02,861 [myid:] - INFO [main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s sessionless connection timeout, 2 selector thread(s), 32 worker threads, and 64 kB direct buffers. [junit] 2015-08-17 17:11:02,861 [myid:] - INFO [main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222 [junit] 2015-08-17 17:11:02,862 [myid:] - INFO [main:ClientBase@355] - STARTING server instance 127.0.0.1:11222 [junit] 2015-08-17 17:11:02,862 [myid:] - INFO [main:ZooKeeperServer@858] - minSessionTimeout set to 6000 [junit] 2015-08-17 17:11:02,862 [myid:] - INFO [main:ZooKeeperServer@867] - maxSessionTimeout set to 6 [junit] 2015-08-17 17:11:02,862 [myid:] - INFO [main:ZooKeeperServer@156] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test2506192539057206720.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test2506192539057206720.junit.dir/version-2 [junit] 2015-08-17 17:11:02,864 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test2506192539057206720.junit.dir/version-2/snapshot.b [junit] 2015-08-17 17:11:02,866 [myid:] - INFO [main:FileTxnSnapLog@298] - Snapshotting: 0xb to /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test2506192539057206720.junit.dir/version-2/snapshot.b [junit] 2015-08-17 17:11:02,868 [myid:] - INFO [main:FourLetterWordMain@84] - connecting to 127.0.0.1 11222 [junit] 2015-08-17 17:11:02,869 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:58841 [junit] 2015-08-17 17:11:02,870 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from /127.0.0.1:58841 [junit] 2015-08-17 17:11:02,870 [myid:] - INFO [NIOWorkerThread-1:StatCommand@49] - Stat command output [junit] 2015-08-17 17:11:02,871 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@606] - Closed socket connection for client /127.0.0.1:58841 (no session established for client) [junit] 2015-08-17 17:11:02,871 [myid:] - INFO [main:JMXEnv@224] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2015-08-17 17:11:02,873 [myid:] - INFO [main:JMXEnv@241] - expect:InMemoryDataTree [junit] 2015-08-17 17:11:02,873 [myid:] - INFO [main:JMXEnv@245] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree [junit] 2015-08-17 17:11:02,874 [myid:] - INFO [main:JMXEnv@241] - expect:StandaloneServer_port [junit] 2015-08-17 17:11:02,874 [myid:] - INFO [main:JMXEnv@245] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11222 [junit] 2015-08-17 17:11:02,874 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 55123 [junit] 2015-08-17 17:11:02,875 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24 [junit] 2015-08-17 17:11:02,875 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD testQuota [junit] 2015-08-17 17:11:02,875 [myid:] - INFO [main:ClientBase@537] - tearDown starting [junit] 2015-08-17 17:11:02,931 [myid:] - INFO [main:ZooKeeper@1110] - Session: 0x1012a5cf7da closed [junit] 2015-08-17 17:11:02,932 [myid:] - INFO [main:ClientBase@507] - STOPPING server [junit] 2015-08-17 17:11:02,931 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@542] - EventThread shut down for session: 0x1012a5cf7da [junit] 2015-08-17 17:11:02,932 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2015-08-17 17:11:02,932 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2015-08-17 17:11:02,932 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@2
[jira] [Commented] (ZOOKEEPER-2249) CRC check failed when preAllocSize smaller than node data
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699791#comment-14699791 ] Benjamin Jaton commented on ZOOKEEPER-2249: --- Something to consider is adding a way to bypass the CRC check to be able to start ZK even if there is a transaction that failed, so that part of the rest of the data can be recovered. I'm thinking about a magical system property like -Dskip.crc.check=true > CRC check failed when preAllocSize smaller than node data > - > > Key: ZOOKEEPER-2249 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2249 > Project: ZooKeeper > Issue Type: Bug >Reporter: Benjamin Jaton > Labels: server > > Unexpected exception, exiting abnormally > java.io.IOException: CRC check failed > org.apache.zookeeper.server.persistence.FileTxnLog$FileTxnIterator.next(FileTxnLog.java:612) > > org.apache.zookeeper.server.persistence.FileTxnSnapLog.restore(FileTxnSnapLog.java:157) > > org.apache.zookeeper.server.ZKDatabase.loadDataBase(ZKDatabase.java:223) > org.apache.zookeeper.server.ZooKeeperServer.loadData(ZooKeeperServer.java:272) > > org.apache.zookeeper.server.ZooKeeperServer.startdata(ZooKeeperServer.java:399) > To reproduce, set the preAllocSize to 8MB, the jute.maxbuffer to 20MB and try > saving a 15MB node several times. > In my case the erroneous CRC appears after the second save. I use the > LogFormatter class to detect it. > I suspect that the CRC error happens when the new transaction log is created, > the code probably expects to have enough room to save the transaction when > creating a new file, but it's too small. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ZOOKEEPER-2249) CRC check failed when preAlloc size smaller than node data
Benjamin Jaton created ZOOKEEPER-2249: - Summary: CRC check failed when preAlloc size smaller than node data Key: ZOOKEEPER-2249 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2249 Project: ZooKeeper Issue Type: Bug Reporter: Benjamin Jaton Unexpected exception, exiting abnormally java.io.IOException: CRC check failed org.apache.zookeeper.server.persistence.FileTxnLog$FileTxnIterator.next(FileTxnLog.java:612) org.apache.zookeeper.server.persistence.FileTxnSnapLog.restore(FileTxnSnapLog.java:157) org.apache.zookeeper.server.ZKDatabase.loadDataBase(ZKDatabase.java:223) org.apache.zookeeper.server.ZooKeeperServer.loadData(ZooKeeperServer.java:272) org.apache.zookeeper.server.ZooKeeperServer.startdata(ZooKeeperServer.java:399) To reproduce, set the preAllocSize to 8MB, the jute.maxbuffer to 20MB and try saving a 15MB node several times. In my case the erroneous CRC appears after the second save. I use the LogFormatter class to detect it. I suspect that the CRC error happens when the new transaction log is created, the code probably expects to have enough room to save the transaction when creating a new file, but it's too small. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ZOOKEEPER-2249) CRC check failed when preAllocSize smaller than node data
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Jaton updated ZOOKEEPER-2249: -- Summary: CRC check failed when preAllocSize smaller than node data (was: CRC check failed when preAlloc size smaller than node data) > CRC check failed when preAllocSize smaller than node data > - > > Key: ZOOKEEPER-2249 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2249 > Project: ZooKeeper > Issue Type: Bug >Reporter: Benjamin Jaton > Labels: server > > Unexpected exception, exiting abnormally > java.io.IOException: CRC check failed > org.apache.zookeeper.server.persistence.FileTxnLog$FileTxnIterator.next(FileTxnLog.java:612) > > org.apache.zookeeper.server.persistence.FileTxnSnapLog.restore(FileTxnSnapLog.java:157) > > org.apache.zookeeper.server.ZKDatabase.loadDataBase(ZKDatabase.java:223) > org.apache.zookeeper.server.ZooKeeperServer.loadData(ZooKeeperServer.java:272) > > org.apache.zookeeper.server.ZooKeeperServer.startdata(ZooKeeperServer.java:399) > To reproduce, set the preAllocSize to 8MB, the jute.maxbuffer to 20MB and try > saving a 15MB node several times. > In my case the erroneous CRC appears after the second save. I use the > LogFormatter class to detect it. > I suspect that the CRC error happens when the new transaction log is created, > the code probably expects to have enough room to save the transaction when > creating a new file, but it's too small. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
ZooKeeper_branch35_jdk7 - Build # 389 - Failure
See https://builds.apache.org/job/ZooKeeper_branch35_jdk7/389/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 369223 lines...] [junit] at org.apache.zookeeper.server.quorum.LearnerHandler.run(LearnerHandler.java:622) [junit] 2015-08-17 13:42:03,015 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:16749:NIOServerCnxnFactory$AcceptThread@219] - accept thread exitted run method [junit] 2015-08-17 13:42:03,015 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2015-08-17 13:42:03,014 [myid:] - WARN [LearnerHandler-/127.0.0.1:36784:LearnerHandler@903] - Ignoring unexpected exception [junit] java.lang.InterruptedException [junit] at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(AbstractQueuedSynchronizer.java:1219) [junit] at java.util.concurrent.locks.ReentrantLock.lockInterruptibly(ReentrantLock.java:340) [junit] at java.util.concurrent.LinkedBlockingQueue.put(LinkedBlockingQueue.java:338) [junit] at org.apache.zookeeper.server.quorum.LearnerHandler.shutdown(LearnerHandler.java:901) [junit] at org.apache.zookeeper.server.quorum.LearnerHandler.run(LearnerHandler.java:622) [junit] 2015-08-17 13:42:03,016 [myid:] - INFO [main-SendThread(127.0.0.1:16652):ClientCnxn$SendThread@1138] - Opening socket connection to server 127.0.0.1/127.0.0.1:16652. Will not attempt to authenticate using SASL (unknown error) [junit] 2015-08-17 13:42:03,015 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2015-08-17 13:42:03,016 [myid:] - INFO [QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:16749)(secure=disabled):MBeanRegistry@119] - Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.5,name2=Leader] [junit] 2015-08-17 13:42:03,016 [myid:] - INFO [/127.0.0.1:16751:QuorumCnxManager$Listener@659] - Leaving listener [junit] 2015-08-17 13:42:03,017 [myid:] - WARN [QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:16749)(secure=disabled):QuorumPeer@1080] - Unexpected exception [junit] java.lang.InterruptedException [junit] at java.lang.Object.wait(Native Method) [junit] at org.apache.zookeeper.server.quorum.Leader.lead(Leader.java:559) [junit] at org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:1077) [junit] 2015-08-17 13:42:03,017 [myid:] - WARN [main-SendThread(127.0.0.1:16652):ClientCnxn$SendThread@1257] - Session 0x301299cad67 for server 127.0.0.1/127.0.0.1:16652, 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:708) [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:355) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1236) [junit] 2015-08-17 13:42:03,017 [myid:] - INFO [QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:16749)(secure=disabled):Leader@613] - Shutting down [junit] 2015-08-17 13:42:03,017 [myid:] - INFO [main:QuorumUtil@254] - Shutting down leader election QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:16749)(secure=disabled) [junit] 2015-08-17 13:42:03,017 [myid:] - WARN [QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:16749)(secure=disabled):QuorumPeer@] - PeerState set to LOOKING [junit] 2015-08-17 13:42:03,018 [myid:] - INFO [main:QuorumUtil@259] - Waiting for QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:16749)(secure=disabled) to exit thread [junit] 2015-08-17 13:42:03,018 [myid:] - WARN [QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:16749)(secure=disabled):QuorumPeer@1093] - QuorumPeer main thread exited [junit] 2015-08-17 13:42:03,018 [myid:] - INFO [QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:16749)(secure=disabled):MBeanRegistry@119] - Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id5] [junit] 2015-08-17 13:42:03,018 [myid:] - INFO [QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:16749)(secure=disabled):MBeanRegistry@119] - Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.5] [junit] 2015-08-17 13:42:03,018 [myid:] - INFO [QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:16749)(secure=disabled):MBeanRegistry@119] - Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.1] [junit] 2015-08-17 13:42:03,018 [myid:] - INFO [QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:16749)(secure=disabled):MBeanRegistry@119] - Unregister MBean [org.apache
ZooKeeper-trunk - Build # 2787 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk/2787/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 372672 lines...] [junit] 2015-08-17 10:52:38,773 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2015-08-17 10:52:38,773 [myid:] - WARN [LearnerHandler-/127.0.0.1:36321:LearnerHandler@903] - Ignoring unexpected exception [junit] java.lang.InterruptedException [junit] at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(AbstractQueuedSynchronizer.java:1219) [junit] at java.util.concurrent.locks.ReentrantLock.lockInterruptibly(ReentrantLock.java:340) [junit] at java.util.concurrent.LinkedBlockingQueue.put(LinkedBlockingQueue.java:338) [junit] at org.apache.zookeeper.server.quorum.LearnerHandler.shutdown(LearnerHandler.java:901) [junit] at org.apache.zookeeper.server.quorum.LearnerHandler.run(LearnerHandler.java:622) [junit] 2015-08-17 10:52:38,774 [myid:] - INFO [QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:19442)(secure=disabled):MBeanRegistry@119] - Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.5,name2=Leader] [junit] 2015-08-17 10:52:38,774 [myid:] - INFO [/127.0.0.1:19444:QuorumCnxManager$Listener@659] - Leaving listener [junit] 2015-08-17 10:52:38,775 [myid:] - WARN [QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:19442)(secure=disabled):QuorumPeer@1080] - Unexpected exception [junit] java.lang.InterruptedException [junit] at java.lang.Object.wait(Native Method) [junit] at org.apache.zookeeper.server.quorum.Leader.lead(Leader.java:559) [junit] at org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:1077) [junit] 2015-08-17 10:52:38,776 [myid:] - INFO [QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:19442)(secure=disabled):Leader@613] - Shutting down [junit] 2015-08-17 10:52:38,776 [myid:] - WARN [QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:19442)(secure=disabled):QuorumPeer@] - PeerState set to LOOKING [junit] 2015-08-17 10:52:38,776 [myid:] - WARN [QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:19442)(secure=disabled):QuorumPeer@1093] - QuorumPeer main thread exited [junit] 2015-08-17 10:52:38,776 [myid:] - INFO [QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:19442)(secure=disabled):MBeanRegistry@119] - Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id5] [junit] 2015-08-17 10:52:38,776 [myid:] - INFO [main:QuorumUtil@254] - Shutting down leader election QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:19442)(secure=disabled) [junit] 2015-08-17 10:52:38,776 [myid:] - INFO [main:QuorumUtil@259] - Waiting for QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:19442)(secure=disabled) to exit thread [junit] 2015-08-17 10:52:38,776 [myid:] - INFO [QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:19442)(secure=disabled):MBeanRegistry@119] - Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.5] [junit] 2015-08-17 10:52:38,777 [myid:] - INFO [QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:19442)(secure=disabled):MBeanRegistry@119] - Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.1] [junit] 2015-08-17 10:52:38,777 [myid:] - INFO [QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:19442)(secure=disabled):MBeanRegistry@119] - Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.2] [junit] 2015-08-17 10:52:38,777 [myid:] - INFO [QuorumPeer[myid=5](plain=/0:0:0:0:0:0:0:0:19442)(secure=disabled):MBeanRegistry@119] - Unregister MBean [org.apache.ZooKeeperService:name0=ReplicatedServer_id5,name1=replica.3] [junit] 2015-08-17 10:52:38,777 [myid:] - INFO [main:FourLetterWordMain@84] - connecting to 127.0.0.1 19430 [junit] 2015-08-17 10:52:38,777 [myid:] - INFO [main:QuorumUtil@243] - 127.0.0.1:19430 is no longer accepting client connections [junit] 2015-08-17 10:52:38,778 [myid:] - INFO [main:FourLetterWordMain@84] - connecting to 127.0.0.1 19433 [junit] 2015-08-17 10:52:38,778 [myid:] - INFO [main:QuorumUtil@243] - 127.0.0.1:19433 is no longer accepting client connections [junit] 2015-08-17 10:52:38,778 [myid:] - INFO [main:FourLetterWordMain@84] - connecting to 127.0.0.1 19436 [junit] 2015-08-17 10:52:38,778 [myid:] - INFO [main:QuorumUtil@243] - 127.0.0.1:19436 is no longer accepting client connections [junit] 2015-08-17 10:52:38,778 [myid:] - INFO [main:FourLetterWordMain@84] - connecting to 127.0.0.1 19439 [junit] 2015-08-17 10:52:38,779 [myid:] - INFO [main:QuorumUtil@243] - 127.0.0.1:19439 is no longer accepting client connections [junit] 2015-08-17 10:52:38,779 [myid:] - INFO [main:FourLetterWordMain@84
ZooKeeper-trunk-solaris - Build # 1072 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-solaris/1072/ ### ## LAST 60 LINES OF THE CONSOLE ### Started by timer Building remotely on solaris1 (Solaris) in workspace /export/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris Updating http://svn.apache.org/repos/asf/zookeeper/trunk at revision '2015-08-17T08:30:00.777 +' At revision 1696212 Updating http://svn.apache.org/repos/asf/hadoop/nightly at revision '2015-08-17T08:30:00.777 +' At revision 1696212 no change for http://svn.apache.org/repos/asf/zookeeper/trunk since the previous build no change for http://svn.apache.org/repos/asf/hadoop/nightly since the previous build No emails were triggered. [locks-and-latches] Checking to see if we really have the locks [locks-and-latches] Have all the locks, build can start [ZooKeeper-trunk-solaris] $ /bin/bash /var/tmp/hudson6604739453270140743.sh FATAL: Cannot find executable from the chosen Ant installation "Ant (latest)" Build step 'Invoke Ant' marked build as failure [locks-and-latches] Releasing all the locks [locks-and-latches] All the locks released Recording test results Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## No tests ran.
