[jira] [Commented] (ZOOKEEPER-1874) Add proper teardown/cleanups in ReconfigTest to shutdown quorumpeer
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13891904#comment-13891904 ] Rakesh R commented on ZOOKEEPER-1874: - Thanks German for the patch. +1 lgtm Add proper teardown/cleanups in ReconfigTest to shutdown quorumpeer --- Key: ZOOKEEPER-1874 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1874 Project: ZooKeeper Issue Type: Sub-task Components: tests Reporter: Rakesh R Fix For: 3.5.0 Attachments: ZOOKEEPER-1874.patch, ZOOKEEPER-1874.patch This jira to provide proper cleanups in ReconfigTest test cases. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
ZooKeeper-3.4-WinVS2008_java - Build # 428 - Still Failing
See https://builds.apache.org/job/ZooKeeper-3.4-WinVS2008_java/428/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 169571 lines...] [junit] 2014-02-05 09:11:58,789 [myid:] - INFO [main:ClientBase@364] - CREATING server instance 127.0.0.1:11221 [junit] 2014-02-05 09:11:58,790 [myid:] - INFO [main:NIOServerCnxnFactory@94] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2014-02-05 09:11:58,791 [myid:] - INFO [main:ClientBase@339] - STARTING server instance 127.0.0.1:11221 [junit] 2014-02-05 09:11:58,791 [myid:] - INFO [main:ZooKeeperServer@162] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir f:\hudson\hudson-slave\workspace\ZooKeeper-3.4-WinVS2008_java\branch-3.4\build\test\tmp\test3704660804769254847.junit.dir\version-2 snapdir f:\hudson\hudson-slave\workspace\ZooKeeper-3.4-WinVS2008_java\branch-3.4\build\test\tmp\test3704660804769254847.junit.dir\version-2 [junit] 2014-02-05 09:11:58,794 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2014-02-05 09:11:58,795 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@197] - Accepted socket connection from /127.0.0.1:57703 [junit] 2014-02-05 09:11:58,795 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing stat command from /127.0.0.1:57703 [junit] 2014-02-05 09:11:58,796 [myid:] - INFO [Thread-4:NIOServerCnxn$StatCommand@663] - Stat command output [junit] 2014-02-05 09:11:58,796 [myid:] - INFO [Thread-4:NIOServerCnxn@1007] - Closed socket connection for client /127.0.0.1:57703 (no session established for client) [junit] 2014-02-05 09:11:58,797 [myid:] - INFO [main:JMXEnv@225] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2014-02-05 09:11:58,798 [myid:] - INFO [main:JMXEnv@242] - expect:InMemoryDataTree [junit] 2014-02-05 09:11:58,798 [myid:] - INFO [main:JMXEnv@246] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2014-02-05 09:11:58,798 [myid:] - INFO [main:JMXEnv@242] - expect:StandaloneServer_port [junit] 2014-02-05 09:11:58,799 [myid:] - INFO [main:JMXEnv@246] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2014-02-05 09:11:58,799 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 10472 [junit] 2014-02-05 09:11:58,799 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 21 [junit] 2014-02-05 09:11:58,799 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota [junit] 2014-02-05 09:11:58,799 [myid:] - INFO [main:ClientBase@520] - tearDown starting [junit] 2014-02-05 09:11:59,089 [myid:] - INFO [main-SendThread(127.0.0.1:11221):ClientCnxn$SendThread@849] - Socket connection established to 127.0.0.1/127.0.0.1:11221, initiating session [junit] 2014-02-05 09:11:59,089 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@197] - Accepted socket connection from /127.0.0.1:57700 [junit] 2014-02-05 09:11:59,090 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:ZooKeeperServer@861] - Client attempting to renew session 0x1440151695b at /127.0.0.1:57700 [junit] 2014-02-05 09:11:59,090 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:ZooKeeperServer@617] - Established session 0x1440151695b with negotiated timeout 3 for client /127.0.0.1:57700 [junit] 2014-02-05 09:11:59,090 [myid:] - INFO [main-SendThread(127.0.0.1:11221):ClientCnxn$SendThread@1228] - Session establishment complete on server 127.0.0.1/127.0.0.1:11221, sessionid = 0x1440151695b, negotiated timeout = 3 [junit] 2014-02-05 09:11:59,091 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@494] - Processed session termination for sessionid: 0x1440151695b [junit] 2014-02-05 09:11:59,091 [myid:] - INFO [SyncThread:0:FileTxnLog@199] - Creating new log file: log.c [junit] 2014-02-05 09:11:59,121 [myid:] - INFO [main:ZooKeeper@684] - Session: 0x1440151695b closed [junit] 2014-02-05 09:11:59,121 [myid:] - INFO [main:ClientBase@490] - STOPPING server [junit] 2014-02-05 09:11:59,121 [myid:] - INFO [main:NIOServerCnxn@1007] - Closed socket connection for client /127.0.0.1:57700 which had sessionid 0x1440151695b [junit] 2014-02-05 09:11:59,122 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@509] - EventThread shut down [junit] 2014-02-05 09:11:59,122 [myid:] - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@357] - caught end of stream exception [junit] EndOfStreamException: Unable to read additional data from
ZooKeeper-trunk-solaris - Build # 811 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-solaris/811/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 216344 lines...] [junit] 2014-02-05 09:52:30,299 [myid:] - INFO [main:SyncRequestProcessor@190] - Shutting down [junit] 2014-02-05 09:52:30,299 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@156] - PrepRequestProcessor exited loop! [junit] 2014-02-05 09:52:30,300 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@168] - SyncRequestProcessor exited! [junit] 2014-02-05 09:52:30,300 [myid:] - INFO [main:FinalRequestProcessor@454] - shutdown of request processor complete [junit] 2014-02-05 09:52:30,300 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2014-02-05 09:52:30,301 [myid:] - INFO [main:JMXEnv@142] - ensureOnly:[] [junit] 2014-02-05 09:52:30,302 [myid:] - INFO [main:ClientBase@443] - STARTING server [junit] 2014-02-05 09:52:30,302 [myid:] - INFO [main:ClientBase@364] - CREATING server instance 127.0.0.1:11221 [junit] 2014-02-05 09:52:30,302 [myid:] - INFO [main:NIOServerCnxnFactory@670] - Configuring NIO connection handler with 10s sessionless connection timeout, 2 selector thread(s), 16 worker threads, and 64 kB direct buffers. [junit] 2014-02-05 09:52:30,303 [myid:] - INFO [main:NIOServerCnxnFactory@683] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2014-02-05 09:52:30,303 [myid:] - INFO [main:ClientBase@339] - STARTING server instance 127.0.0.1:11221 [junit] 2014-02-05 09:52:30,303 [myid:] - INFO [main:ZooKeeperServer@149] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test4556934193442520161.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test4556934193442520161.junit.dir/version-2 [junit] 2014-02-05 09:52:30,304 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test4556934193442520161.junit.dir/version-2/snapshot.b [junit] 2014-02-05 09:52:30,307 [myid:] - INFO [main:FileTxnSnapLog@297] - Snapshotting: 0xb to /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test4556934193442520161.junit.dir/version-2/snapshot.b [junit] 2014-02-05 09:52:30,308 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2014-02-05 09:52:30,309 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:56389 [junit] 2014-02-05 09:52:30,309 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@835] - Processing stat command from /127.0.0.1:56389 [junit] 2014-02-05 09:52:30,309 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn$StatCommand@684] - Stat command output [junit] 2014-02-05 09:52:30,310 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@1006] - Closed socket connection for client /127.0.0.1:56389 (no session established for client) [junit] 2014-02-05 09:52:30,310 [myid:] - INFO [main:JMXEnv@224] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2014-02-05 09:52:30,311 [myid:] - INFO [main:JMXEnv@241] - expect:InMemoryDataTree [junit] 2014-02-05 09:52:30,311 [myid:] - INFO [main:JMXEnv@245] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2014-02-05 09:52:30,311 [myid:] - INFO [main:JMXEnv@241] - expect:StandaloneServer_port [junit] 2014-02-05 09:52:30,312 [myid:] - INFO [main:JMXEnv@245] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2014-02-05 09:52:30,312 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 13366 [junit] 2014-02-05 09:52:30,312 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 24 [junit] 2014-02-05 09:52:30,312 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota [junit] 2014-02-05 09:52:30,312 [myid:] - INFO [main:ClientBase@520] - tearDown starting [junit] 2014-02-05 09:52:30,388 [myid:] - INFO [main:ZooKeeper@954] - Session: 0x14401768b23 closed [junit] 2014-02-05 09:52:30,389 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@533] - EventThread shut down [junit] 2014-02-05 09:52:30,389 [myid:] - INFO [main:ClientBase@490] - STOPPING server [junit] 2014-02-05 09:52:30,389 [myid:] - INFO
[jira] [Commented] (BOOKKEEPER-724) Shade introduces RAT error
[ https://issues.apache.org/jira/browse/BOOKKEEPER-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13891959#comment-13891959 ] Sijie Guo commented on BOOKKEEPER-724: -- I am just wondering how other apache projects handling this ? [~fpj] [~ikelly] Shade introduces RAT error -- Key: BOOKKEEPER-724 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-724 Project: Bookkeeper Issue Type: Bug Reporter: Sijie Guo Priority: Blocker Fix For: 4.3.0 Shading library in BOOKKEEPER-708 introduces an unlicensed pom file for bookkeeper-server module. we should address this, otherwise we could not publish the new jar per apache release procedure. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
ZooKeeper-trunk-WinVS2008_java - Build # 674 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008_java/674/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 238913 lines...] [junit] 2014-02-05 10:25:27,530 [myid:] - INFO [main-SendThread(127.0.0.1:11221):ClientCnxn$SendThread@1094] - Opening socket connection to server 127.0.0.1/127.0.0.1:11221. Will not attempt to authenticate using SASL (unknown error) [junit] 2014-02-05 10:25:27,596 [myid:] - INFO [main:JMXEnv@142] - ensureOnly:[] [junit] 2014-02-05 10:25:27,597 [myid:] - INFO [main:ClientBase@443] - STARTING server [junit] 2014-02-05 10:25:27,597 [myid:] - INFO [main:ClientBase@364] - CREATING server instance 127.0.0.1:11221 [junit] 2014-02-05 10:25:27,597 [myid:] - INFO [main:NIOServerCnxnFactory@670] - Configuring NIO connection handler with 10s sessionless connection timeout, 1 selector thread(s), 4 worker threads, and 64 kB direct buffers. [junit] 2014-02-05 10:25:27,598 [myid:] - INFO [main:NIOServerCnxnFactory@683] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2014-02-05 10:25:27,599 [myid:] - INFO [main:ClientBase@339] - STARTING server instance 127.0.0.1:11221 [junit] 2014-02-05 10:25:27,600 [myid:] - INFO [main:ZooKeeperServer@149] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008_java\trunk\build\test\tmp\test4250696936934269743.junit.dir\version-2 snapdir f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008_java\trunk\build\test\tmp\test4250696936934269743.junit.dir\version-2 [junit] 2014-02-05 10:25:27,601 [myid:] - INFO [main:FileSnap@83] - Reading snapshot f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008_java\trunk\build\test\tmp\test4250696936934269743.junit.dir\version-2\snapshot.b [junit] 2014-02-05 10:25:27,603 [myid:] - INFO [main:FileTxnSnapLog@297] - Snapshotting: 0xb to f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008_java\trunk\build\test\tmp\test4250696936934269743.junit.dir\version-2\snapshot.b [junit] 2014-02-05 10:25:27,604 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2014-02-05 10:25:27,605 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:60043 [junit] 2014-02-05 10:25:27,605 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@835] - Processing stat command from /127.0.0.1:60043 [junit] 2014-02-05 10:25:27,606 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn$StatCommand@684] - Stat command output [junit] 2014-02-05 10:25:27,606 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@1006] - Closed socket connection for client /127.0.0.1:60043 (no session established for client) [junit] 2014-02-05 10:25:27,606 [myid:] - INFO [main:JMXEnv@224] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2014-02-05 10:25:27,608 [myid:] - INFO [main:JMXEnv@241] - expect:InMemoryDataTree [junit] 2014-02-05 10:25:27,608 [myid:] - INFO [main:JMXEnv@245] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2014-02-05 10:25:27,608 [myid:] - INFO [main:JMXEnv@241] - expect:StandaloneServer_port [junit] 2014-02-05 10:25:27,608 [myid:] - INFO [main:JMXEnv@245] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2014-02-05 10:25:27,608 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 13380 [junit] 2014-02-05 10:25:27,609 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 22 [junit] 2014-02-05 10:25:27,609 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota [junit] 2014-02-05 10:25:27,609 [myid:] - INFO [main:ClientBase@520] - tearDown starting [junit] 2014-02-05 10:25:28,028 [myid:] - INFO [main-SendThread(127.0.0.1:11221):ClientCnxn$SendThread@968] - Socket connection established to 127.0.0.1/127.0.0.1:11221, initiating session [junit] 2014-02-05 10:25:28,028 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:60038 [junit] 2014-02-05 10:25:28,029 [myid:] - INFO [NIOWorkerThread-2:ZooKeeperServer@858] - Client attempting to renew session 0x1440194af18 at /127.0.0.1:60038 [junit] 2014-02-05 10:25:28,030 [myid:] - INFO [NIOWorkerThread-2:ZooKeeperServer@604] - Established session 0x1440194af18 with negotiated timeout 3 for client /127.0.0.1:60038 [junit] 2014-02-05 10:25:28,030 [myid:] - INFO [main-SendThread(127.0.0.1:11221):ClientCnxn$SendThread@1347] - Session
[jira] [Commented] (ZOOKEEPER-1473) Committed proposal log retains triple the memory it needs to
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13892033#comment-13892033
]
Mathias H. commented on ZOOKEEPER-1473:
---
Any chance to get this patch into the next release?
Committed proposal log retains triple the memory it needs to
Key: ZOOKEEPER-1473
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1473
Project: ZooKeeper
Issue Type: Bug
Components: server
Reporter: Henry Robinson
Assignee: Thawan Kooburat
Fix For: 3.5.0
Attachments: ZOOKEEPER-1473.patch, ZOOKEEPER-1473.patch
ZKDatabase.committedLog retains the past 500 transactions to enable fast
catch-up. This works great, but it's using triple the memory it needs to by
retaining three copies of the data part of any transaction.
* The first is in committedLog[i].request.request.hb - a heap-allocated
{{ByteBuffer}}.
* The second is in committedLog[i].request.txn.data - a jute-serialised
record of the transaction
* The third is in committedLog[i].packet.data - also jute-serialised,
seemingly uninitialised data.
This means that a ZK-server could be using 1G of memory more than it should
be in the worst case. We should use just one copy of the data, even if we
really have to refer to it 3 times.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
Failed: ZOOKEEPER-1473 PreCommit Build #1918
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1473 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1918/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 67 lines...] [exec] [exec] [exec] patching file src/java/main/org/apache/zookeeper/server/ZKDatabase.java [exec] Hunk #1 succeeded at 66 (offset 3 lines). [exec] Hunk #2 FAILED at 81. [exec] Hunk #3 succeeded at 243 (offset 10 lines). [exec] Hunk #4 succeeded at 274 (offset 10 lines). [exec] 1 out of 4 hunks FAILED -- saving rejects to file src/java/main/org/apache/zookeeper/server/ZKDatabase.java.rej [exec] PATCH APPLICATION FAILED [exec] [exec] [exec] [exec] [exec] -1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12578459/ZOOKEEPER-1473.patch [exec] against trunk revision 1561672. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [exec] [exec] -1 patch. The patch command could not apply the patch. [exec] [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1918//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] 7ea64b75065c0196c4863e4f35ba00c5f2e27f2e logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1674: exec returned: 1 Total time: 56 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Recording test results Description set: ZOOKEEPER-1473 Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Commented] (ZOOKEEPER-1473) Committed proposal log retains triple the memory it needs to
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13892036#comment-13892036
]
Hadoop QA commented on ZOOKEEPER-1473:
--
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12578459/ZOOKEEPER-1473.patch
against trunk revision 1561672.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1918//console
This message is automatically generated.
Committed proposal log retains triple the memory it needs to
Key: ZOOKEEPER-1473
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1473
Project: ZooKeeper
Issue Type: Bug
Components: server
Reporter: Henry Robinson
Assignee: Thawan Kooburat
Fix For: 3.5.0
Attachments: ZOOKEEPER-1473.patch, ZOOKEEPER-1473.patch
ZKDatabase.committedLog retains the past 500 transactions to enable fast
catch-up. This works great, but it's using triple the memory it needs to by
retaining three copies of the data part of any transaction.
* The first is in committedLog[i].request.request.hb - a heap-allocated
{{ByteBuffer}}.
* The second is in committedLog[i].request.txn.data - a jute-serialised
record of the transaction
* The third is in committedLog[i].packet.data - also jute-serialised,
seemingly uninitialised data.
This means that a ZK-server could be using 1G of memory more than it should
be in the worst case. We should use just one copy of the data, even if we
really have to refer to it 3 times.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (ZOOKEEPER-1460) IPv6 literal address not supported for quorum members
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13892280#comment-13892280
]
Liping commented on ZOOKEEPER-1460:
---
Hi
Is anyone looking into this issue?
In our env, we do not want to depend on dns. So it is better if we have an
official fix for it. Thanks.
Liping
IPv6 literal address not supported for quorum members
-
Key: ZOOKEEPER-1460
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1460
Project: ZooKeeper
Issue Type: Bug
Components: quorum
Affects Versions: 3.4.3
Reporter: Chris Dolan
Via code inspection, I see that the server.nnn configuration key does not
support literal IPv6 addresses because the property value is split on :. In
v3.4.3, the problem is in QuorumPeerConfig:
{noformat}
String parts[] = value.split(:);
InetSocketAddress addr = new InetSocketAddress(parts[0],
Integer.parseInt(parts[1]));
{noformat}
In the current trunk
(http://svn.apache.org/viewvc/zookeeper/trunk/src/java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java?view=markup)
this code has been refactored into QuorumPeer.QuorumServer, but the bug
remains:
{noformat}
String serverClientParts[] = addressStr.split(;);
String serverParts[] = serverClientParts[0].split(:);
addr = new InetSocketAddress(serverParts[0],
Integer.parseInt(serverParts[1]));
{noformat}
This bug probably affects very few users because most will naturally use a
hostname rather than a literal IP address. But given that IPv6 addresses are
supported for clients via ZOOKEEPER-667 it seems that server support should
be fixed too.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
Failed: ZOOKEEPER-1848 PreCommit Build #1919
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1848 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1919/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 75 lines...] [exec] 2 out of 2 hunks FAILED -- saving rejects to file bin/zkEnv.cmd.rej [exec] patching file bin/zkServer.cmd [exec] Hunk #1 FAILED at 17. [exec] 1 out of 1 hunk FAILED -- saving rejects to file bin/zkServer.cmd.rej [exec] patching file build.xml [exec] Hunk #1 succeeded at 1274 (offset 51 lines). [exec] Hunk #2 succeeded at 1296 (offset 51 lines). [exec] patching file conf/zookeeper-env.cmd [exec] PATCH APPLICATION FAILED [exec] [exec] [exec] [exec] [exec] -1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12627041/zookeeper-1848_v1.patch [exec] against trunk revision 1561672. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] -1 tests included. The patch doesn't appear to include any new or modified tests. [exec] Please justify why no new tests are needed for this patch. [exec] Also please list what manual steps were performed to verify this patch. [exec] [exec] -1 patch. The patch command could not apply the patch. [exec] [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1919//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] 396e1a35d244a915e91d05e4e85dc66c89b4ce45 logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD FAILED /home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1674: exec returned: 1 Total time: 43 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Recording test results Description set: ZOOKEEPER-1848 Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Commented] (ZOOKEEPER-1848) [WINDOWS] Java NIO socket channels does not work with Windows ipv6 on JDK6
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13892326#comment-13892326 ] Hadoop QA commented on ZOOKEEPER-1848: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12627041/zookeeper-1848_v1.patch against trunk revision 1561672. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1919//console This message is automatically generated. [WINDOWS] Java NIO socket channels does not work with Windows ipv6 on JDK6 -- Key: ZOOKEEPER-1848 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1848 Project: ZooKeeper Issue Type: Bug Reporter: Enis Soztutar Assignee: Enis Soztutar Fix For: 3.5.0 Attachments: zookeeper-1848_v1.patch ZK uses Java NIO to create ServerSorcket's from ServerSocketChannels. Under windows, the ipv4 and ipv6 is implemented independently, and Java seems that it cannot reuse the same socket channel for both ipv4 and ipv6 sockets. We are getting java.net.SocketException: Address family not supported by protocol family exceptions. When, ZK client resolves localhost, it gets both v4 127.0.0.1 and v6 ::1 address, but the socket channel cannot bind to both v4 and v6. The problem is reported as: http://bugs.sun.com/view_bug.do?bug_id=6230761 http://stackoverflow.com/questions/1357091/binding-an-ipv6-server-socket-on-windows Although the JDK bug is reported as resolved, I have tested with jdk1.6.0_33 without any success. Although JDK7 seems to have fixed this problem. See HBASE-6825 for reference. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (ZOOKEEPER-1833) fix windows build
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flavio Junqueira updated ZOOKEEPER-1833:
Attachment: LeaderSessionTrackerTest-output.txt
Here is one. It gets stuck when connecting.
fix windows build
-
Key: ZOOKEEPER-1833
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1833
Project: ZooKeeper
Issue Type: Bug
Affects Versions: 3.4.5
Reporter: Michi Mutsuzaki
Assignee: Michi Mutsuzaki
Priority: Blocker
Fix For: 3.4.6
Attachments: LeaderSessionTrackerTest-output.txt,
TEST-org.apache.zookeeper.test.QuorumTest.zip, ZOOKEEPER-1833-b3.4.patch,
ZOOKEEPER-1833.patch, ZOOKEEPER-1833.patch
A bunch of 3.4 tests are failing on windows.
{noformat}
[junit] 2013-12-06 08:40:59,692 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testEarlyLeaderAbandonment
[junit] 2013-12-06 08:41:10,472 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testHighestZxidJoinLate
[junit] 2013-12-06 08:45:31,085 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testUpdatingEpoch
[junit] 2013-12-06 08:55:34,630 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testObserversHammer
[junit] 2013-12-06 08:55:59,889 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncExistsFailure_NoNode
[junit] 2013-12-06 08:56:00,571 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetACL
[junit] 2013-12-06 08:56:02,626 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetChildrenEmpty
[junit] 2013-12-06 08:56:03,491 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetChildrenSingle
[junit] 2013-12-06 08:56:11,276 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetChildrenTwo
[junit] 2013-12-06 08:56:13,878 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetChildrenFailure_NoNode
[junit] 2013-12-06 08:56:16,294 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetChildren2Empty
[junit] 2013-12-06 08:56:18,622 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetChildren2Single
[junit] 2013-12-06 08:56:21,224 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetChildren2Two
[junit] 2013-12-06 08:56:23,738 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetChildren2Failure_NoNode
[junit] 2013-12-06 08:56:26,058 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetData
[junit] 2013-12-06 08:56:28,482 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetDataFailure_NoNode
[junit] 2013-12-06 08:57:35,527 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testStartupFailureCreate
[junit] 2013-12-06 08:57:38,645 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testStartupFailureSet
[junit] 2013-12-06 08:57:41,261 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testStartupFailureSnapshot
[junit] 2013-12-06 08:59:22,222 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testClientWithWatcherObj
[junit] 2013-12-06 09:00:05,592 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testClientCleanup
[junit] 2013-12-06 09:01:24,113 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testBindByAddress
[junit] 2013-12-06 09:02:14,123 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testClientwithoutWatcherObj
[junit] 2013-12-06 09:05:56,461 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testZeroWeightQuorum
[junit] 2013-12-06 09:08:18,747 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testResyncByDiffAfterFollowerCrashes
[junit] 2013-12-06 09:09:42,271 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testFourLetterWords
[junit] 2013-12-06 09:14:03,770 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testLE
[junit] 2013-12-06 09:46:30,002 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testHierarchicalQuorum
[junit] 2013-12-06 09:50:26,912 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testHammerBasic
[junit] 2013-12-06 09:51:07,604 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testQuotaWithQuorum
[junit] 2013-12-06 09:52:41,515 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testNull
[junit] 2013-12-06 09:53:22,648 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testDeleteWithChildren
[junit] 2013-12-06 09:56:49,061 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testClientwithoutWatcherObj
[junit] 2013-12-06 09:58:27,705 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testGetView
[junit] 2013-12-06 09:59:07,856 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testViewContains
[junit] 2013-12-06 10:01:31,418 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testSessionMoved
[junit] 2013-12-06 10:04:50,542 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testMultiToFollower
[jira] [Commented] (ZOOKEEPER-1869) zk server falling apart from quorum due to connection loss and couldn't connect back
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13892790#comment-13892790 ] Deepak Jagtap commented on ZOOKEEPER-1869: -- Hi German, Unfortunately this issue occurred at customer site and hence difficult to reproduce it. If we managed to reproduce this in the lab will update you with new set of logs. Thanks Regards, Deepak zk server falling apart from quorum due to connection loss and couldn't connect back Key: ZOOKEEPER-1869 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1869 Project: ZooKeeper Issue Type: Bug Components: quorum Affects Versions: 3.5.0 Environment: Using CentOS6 for running these zookeeper servers Reporter: Deepak Jagtap Priority: Critical We have deployed zookeeper version 3.5.0.1515976, with 3 zk servers in the quorum. The problem we are facing is that one zookeeper server in the quorum falls apart, and never becomes part of the cluster until we restart zookeeper server on that node. Our interpretation from zookeeper logs on all nodes is as follows: (For simplicity assume S1= zk server1, S2 = zk server2, S3 = zk server 3) Initially S3 is the leader while S1 and S2 are followers. S2 hits 46 sec latency while fsyncing write ahead log and results in loss of connection with S3. S3 in turn prints following error message: Unexpected exception causing shutdown while sock still open java.net.SocketTimeoutException: Read timed out Stack trace *** GOODBYE /169.254.1.2:47647(S2) S2 in this case closes connection with S3(leader) and shuts down follower with following log messages: Closing connection to leader, exception during packet send java.net.SocketException: Socket close Follower@194] - shutdown called java.lang.Exception: shutdown Follower After this point S3 could never reestablish connection with S2 and leader election mechanism keeps failing. S3 now keeps printing following message repeatedly: Cannot open channel to 2 at election address /169.254.1.2:3888 java.net.ConnectException: Connection refused. While S3 is in this state, S2 repeatedly keeps printing following message: INFO [NIOServerCxnFactory.AcceptThread:/0.0.0.0:2181:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:60667 Exception causing close of session 0x0: ZooKeeperServer not running Closed socket connection for client /127.0.0.1:60667 (no session established for client) Leader election never completes successfully and causing S2 to fall apart from the quorum. S2 was out of quorum for almost 1 week. While debugging this issue, we found out that both election and peer connection ports on S2 can't be telneted from any of the node (S1, S2, S3). Network connectivity is not the issue. Later, we restarted the ZK server S2 (service zookeeper-server restart) -- now we could telnet to both the ports and S2 joined the ensemble after a leader election attempt. Any idea what might be forcing S2 to get into a situation where it won't accept any connections on the leader election and peer connection ports? -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (ZOOKEEPER-1833) fix windows build
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13892961#comment-13892961
]
Rakesh R commented on ZOOKEEPER-1833:
-
Normally after the quorumpeer shutdown, test is expecting to get the connection
exception when trying to connect to this server:
{code}
'java.net.ConnectException: Connection refused: connect' when executing Socket
sock = new Socket(host, port);
{code}
and after that move on to the next. But as mentioned its stuck over there, it
would be helpful if we have the thread dump to analyse more.
Also, this 'qu.startAll() or qu.startQuorum()' flow is common to many test
cases like WatchEventWhenAutoReset, ReconfigTest et. I'm just thinking in your
env whether all these tests are getting stuck at this point.
fix windows build
-
Key: ZOOKEEPER-1833
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1833
Project: ZooKeeper
Issue Type: Bug
Affects Versions: 3.4.5
Reporter: Michi Mutsuzaki
Assignee: Michi Mutsuzaki
Priority: Blocker
Fix For: 3.4.6
Attachments: LeaderSessionTrackerTest-output.txt,
TEST-org.apache.zookeeper.test.QuorumTest.zip, ZOOKEEPER-1833-b3.4.patch,
ZOOKEEPER-1833.patch, ZOOKEEPER-1833.patch
A bunch of 3.4 tests are failing on windows.
{noformat}
[junit] 2013-12-06 08:40:59,692 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testEarlyLeaderAbandonment
[junit] 2013-12-06 08:41:10,472 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testHighestZxidJoinLate
[junit] 2013-12-06 08:45:31,085 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testUpdatingEpoch
[junit] 2013-12-06 08:55:34,630 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testObserversHammer
[junit] 2013-12-06 08:55:59,889 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncExistsFailure_NoNode
[junit] 2013-12-06 08:56:00,571 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetACL
[junit] 2013-12-06 08:56:02,626 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetChildrenEmpty
[junit] 2013-12-06 08:56:03,491 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetChildrenSingle
[junit] 2013-12-06 08:56:11,276 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetChildrenTwo
[junit] 2013-12-06 08:56:13,878 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetChildrenFailure_NoNode
[junit] 2013-12-06 08:56:16,294 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetChildren2Empty
[junit] 2013-12-06 08:56:18,622 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetChildren2Single
[junit] 2013-12-06 08:56:21,224 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetChildren2Two
[junit] 2013-12-06 08:56:23,738 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetChildren2Failure_NoNode
[junit] 2013-12-06 08:56:26,058 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetData
[junit] 2013-12-06 08:56:28,482 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testAsyncGetDataFailure_NoNode
[junit] 2013-12-06 08:57:35,527 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testStartupFailureCreate
[junit] 2013-12-06 08:57:38,645 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testStartupFailureSet
[junit] 2013-12-06 08:57:41,261 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testStartupFailureSnapshot
[junit] 2013-12-06 08:59:22,222 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testClientWithWatcherObj
[junit] 2013-12-06 09:00:05,592 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testClientCleanup
[junit] 2013-12-06 09:01:24,113 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testBindByAddress
[junit] 2013-12-06 09:02:14,123 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testClientwithoutWatcherObj
[junit] 2013-12-06 09:05:56,461 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testZeroWeightQuorum
[junit] 2013-12-06 09:08:18,747 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testResyncByDiffAfterFollowerCrashes
[junit] 2013-12-06 09:09:42,271 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testFourLetterWords
[junit] 2013-12-06 09:14:03,770 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testLE
[junit] 2013-12-06 09:46:30,002 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testHierarchicalQuorum
[junit] 2013-12-06 09:50:26,912 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testHammerBasic
[junit] 2013-12-06 09:51:07,604 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testQuotaWithQuorum
[junit] 2013-12-06 09:52:41,515 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testNull
[junit] 2013-12-06 09:53:22,648 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED
[jira] [Commented] (BOOKKEEPER-724) Shade introduces RAT error
[ https://issues.apache.org/jira/browse/BOOKKEEPER-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13891950#comment-13891950 ] Flavio Junqueira commented on BOOKKEEPER-724: - Just so that I understand. The sources release doesn't have to contain the reduced pom because it can be generated from the main pom file. If we need to release with it, I assume that it would be for the binary artifacts. Is this right? For the binary artifacts, could we introduce it manually? Not idea and error prone, but seems doable. We need to exclude at least to have QA passing when we submit patches. Shade introduces RAT error -- Key: BOOKKEEPER-724 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-724 Project: Bookkeeper Issue Type: Bug Reporter: Sijie Guo Priority: Blocker Fix For: 4.3.0 Shading library in BOOKKEEPER-708 introduces an unlicensed pom file for bookkeeper-server module. we should address this, otherwise we could not publish the new jar per apache release procedure. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (BOOKKEEPER-644) Provide a bookie address wrapper
[ https://issues.apache.org/jira/browse/BOOKKEEPER-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13892606#comment-13892606 ] Flavio Junqueira commented on BOOKKEEPER-644: - I'm not sure why QA didn't run, but the latest result is good already. +1, it looks good to me. Provide a bookie address wrapper Key: BOOKKEEPER-644 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-644 Project: Bookkeeper Issue Type: Sub-task Components: bookkeeper-client, bookkeeper-server Reporter: Sijie Guo Assignee: Sijie Guo Fix For: 4.3.0 Attachments: BOOKKEEPER-644.diff, BOOKKEEPER-644.diff, BOOKKEEPER-644.diff, BOOKKEEPER-644.diff, BOOKKEEPER-644.diff, BOOKKEEPER-644.diff Provide bookie address wrapper for BOOKKEEPER-629, so client would use the address identifier by server w/o involving in deciding using ip or hostname. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (BOOKKEEPER-644) Provide a bookie address wrapper
[ https://issues.apache.org/jira/browse/BOOKKEEPER-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13892637#comment-13892637 ] Hudson commented on BOOKKEEPER-644: --- SUCCESS: Integrated in bookkeeper-trunk #538 (See [https://builds.apache.org/job/bookkeeper-trunk/538/]) BOOKKEEPER-644: Provide a bookie address wrapper (sijie via fpj) (fpj: rev 1564946) * /zookeeper/bookkeeper/trunk/CHANGES.txt * /zookeeper/bookkeeper/trunk/bookkeeper-benchmark/src/main/java/org/apache/bookkeeper/benchmark/BenchBookie.java * /zookeeper/bookkeeper/trunk/bookkeeper-benchmark/src/test/java/org/apache/bookkeeper/benchmark/TestBenchmark.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/Bookie.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/BookieShell.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/Cookie.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/BookKeeperAdmin.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/BookieWatcher.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/DefaultEnsemblePlacementPolicy.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/EnsemblePlacementPolicy.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/LedgerChecker.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/LedgerCreateOp.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/LedgerFragment.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/LedgerFragmentReplicator.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/LedgerHandle.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/LedgerMetadata.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/PendingAddOp.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/PendingReadOp.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/RackawareEnsemblePlacementPolicy.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/ReadOnlyLedgerHandle.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/net/BookieSocketAddress.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/BookieClient.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/BookieNettyServer.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/BookieRequestHandler.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/BookieRequestProcessor.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/BookieServer.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/BookieServerBean.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/BookkeeperInternalCallbacks.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/PerChannelBookieClient.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/replication/Auditor.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/replication/AutoRecoveryMain.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/replication/BookieLedgerIndexer.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/replication/ReplicationWorker.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/tools/BookKeeperTools.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/util/StringUtils.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/test/java/org/apache/bookkeeper/client/BookieRecoveryTest.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/test/java/org/apache/bookkeeper/client/BookieWriteLedgerTest.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/test/java/org/apache/bookkeeper/client/LedgerCloseTest.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/test/java/org/apache/bookkeeper/client/LedgerRecoveryTest.java * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/test/java/org/apache/bookkeeper/client/SlowBookieTest.java *
[jira] [Commented] (BOOKKEEPER-727) Names of bookie write/read threads are backwards
[ https://issues.apache.org/jira/browse/BOOKKEEPER-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13892705#comment-13892705 ] Hudson commented on BOOKKEEPER-727: --- SUCCESS: Integrated in bookkeeper-trunk #539 (See [https://builds.apache.org/job/bookkeeper-trunk/539/]) BOOKKEEPER-727: Names of bookie write/read threads are backwards (ivank via fpj) (fpj: rev 1564949) * /zookeeper/bookkeeper/trunk/CHANGES.txt * /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/BookieRequestProcessor.java Names of bookie write/read threads are backwards Key: BOOKKEEPER-727 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-727 Project: Bookkeeper Issue Type: Bug Reporter: Ivan Kelly Assignee: Ivan Kelly Fix For: 4.3.0 Attachments: 0003-BOOKKEEPER-727-Names-of-bookie-threads-are-wrong.patch Summary says it all. Thread factories are backwards. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
