ZooKeeper_branch34_solaris - Build # 753 - Failure
See https://builds.apache.org/job/ZooKeeper_branch34_solaris/753/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 146749 lines...] [junit] 2013-12-30 08:09:06,121 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2013-12-30 08:09:06,121 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2013-12-30 08:09:06,121 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2013-12-30 08:09:06,121 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-12-30 08:09:06,121 [myid:] - INFO [main:ClientBase@420] - STOPPING server [junit] 2013-12-30 08:09:06,122 [myid:] - INFO [main:ZooKeeperServer@441] - shutting down [junit] 2013-12-30 08:09:06,122 [myid:] - INFO [main:SessionTrackerImpl@225] - Shutting down [junit] 2013-12-30 08:09:06,122 [myid:] - INFO [main:PrepRequestProcessor@761] - Shutting down [junit] 2013-12-30 08:09:06,122 [myid:] - INFO [main:SyncRequestProcessor@209] - Shutting down [junit] 2013-12-30 08:09:06,122 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop! [junit] 2013-12-30 08:09:06,122 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited! [junit] 2013-12-30 08:09:06,123 [myid:] - INFO [main:FinalRequestProcessor@415] - shutdown of request processor complete [junit] 2013-12-30 08:09:06,123 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-12-30 08:09:06,124 [myid:] - INFO [main:JMXEnv@135] - ensureOnly:[] [junit] 2013-12-30 08:09:06,125 [myid:] - INFO [main:ClientBase@413] - STARTING server [junit] 2013-12-30 08:09:06,125 [myid:] - INFO [main:ZooKeeperServer@162] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/trunk/build/test/tmp/test4318699480841147001.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/trunk/build/test/tmp/test4318699480841147001.junit.dir/version-2 [junit] 2013-12-30 08:09:06,126 [myid:] - INFO [main:NIOServerCnxnFactory@94] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2013-12-30 08:09:06,129 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-12-30 08:09:06,130 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@197] - Accepted socket connection from /127.0.0.1:53975 [junit] 2013-12-30 08:09:06,130 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing stat command from /127.0.0.1:53975 [junit] 2013-12-30 08:09:06,130 [myid:] - INFO [Thread-5:NIOServerCnxn$StatCommand@663] - Stat command output [junit] 2013-12-30 08:09:06,131 [myid:] - INFO [Thread-5:NIOServerCnxn@1007] - Closed socket connection for client /127.0.0.1:53975 (no session established for client) [junit] 2013-12-30 08:09:06,131 [myid:] - INFO [main:JMXEnv@135] - ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] 2013-12-30 08:09:06,132 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2013-12-30 08:09:06,132 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2013-12-30 08:09:06,133 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2013-12-30 08:09:06,133 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-12-30 08:09:06,135 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 8563 [junit] 2013-12-30 08:09:06,135 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 20 [junit] 2013-12-30 08:09:06,135 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota [junit] 2013-12-30 08:09:06,135 [myid:] - INFO [main:ClientBase@450] - tearDown starting [junit] 2013-12-30 08:09:06,210 [myid:] - INFO [main:ZooKeeper@684] - Session: 0x143428c94b2 closed [junit] 2013-12-30 08:09:06,210 [myid:] - INFO [main:ClientBase@420] - STOPPING server [junit] 2013-12-30 08:09:06,210 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@509] - EventThread shut down [junit] 2013-12-30 08:09:06,212 [myid:] - INFO [main:ZooKeeperServer@441] - shutting down [junit] 2013-12-30 08:09:06,212 [myid:] - INFO [main:SessionTrackerImpl@225] -
ZooKeeper-trunk-solaris - Build # 776 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-solaris/776/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 208478 lines...] [junit] 2013-12-30 09:08:54,555 [myid:] - INFO [main:SessionTrackerImpl@183] - Shutting down [junit] 2013-12-30 09:08:54,555 [myid:] - INFO [main:PrepRequestProcessor@972] - Shutting down [junit] 2013-12-30 09:08:54,555 [myid:] - INFO [main:SyncRequestProcessor@190] - Shutting down [junit] 2013-12-30 09:08:54,555 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@156] - PrepRequestProcessor exited loop! [junit] 2013-12-30 09:08:54,555 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@168] - SyncRequestProcessor exited! [junit] 2013-12-30 09:08:54,555 [myid:] - INFO [main:FinalRequestProcessor@442] - shutdown of request processor complete [junit] 2013-12-30 09:08:54,556 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-12-30 09:08:54,556 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[] [junit] 2013-12-30 09:08:54,557 [myid:] - INFO [main:ClientBase@414] - STARTING server [junit] 2013-12-30 09:08:54,558 [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/test2032500173245020069.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test2032500173245020069.junit.dir/version-2 [junit] 2013-12-30 09:08:54,558 [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] 2013-12-30 09:08:54,559 [myid:] - INFO [main:NIOServerCnxnFactory@683] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2013-12-30 09:08:54,559 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test2032500173245020069.junit.dir/version-2/snapshot.b [junit] 2013-12-30 09:08:54,562 [myid:] - INFO [main:FileTxnSnapLog@297] - Snapshotting: 0xb to /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test2032500173245020069.junit.dir/version-2/snapshot.b [junit] 2013-12-30 09:08:54,563 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-12-30 09:08:54,564 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:65165 [junit] 2013-12-30 09:08:54,564 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@835] - Processing stat command from /127.0.0.1:65165 [junit] 2013-12-30 09:08:54,564 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn$StatCommand@684] - Stat command output [junit] 2013-12-30 09:08:54,565 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@1006] - Closed socket connection for client /127.0.0.1:65165 (no session established for client) [junit] 2013-12-30 09:08:54,565 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] 2013-12-30 09:08:54,566 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2013-12-30 09:08:54,566 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2013-12-30 09:08:54,566 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2013-12-30 09:08:54,567 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-12-30 09:08:54,567 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 13412 [junit] 2013-12-30 09:08:54,567 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 24 [junit] 2013-12-30 09:08:54,567 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota [junit] 2013-12-30 09:08:54,567 [myid:] - INFO [main:ClientBase@451] - tearDown starting [junit] 2013-12-30 09:08:54,641 [myid:] - INFO [main:ZooKeeper@777] - Session: 0x14342c3550f closed [junit] 2013-12-30 09:08:54,641 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down [junit] 2013-12-30 09:08:54,641 [myid:] - INFO [main:ClientBase@421] - STOPPING server [junit] 2013-12-30 09:08:54,642 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@219] -
ZooKeeper-3.4-WinVS2008_java - Build # 393 - Still Failing
See https://builds.apache.org/job/ZooKeeper-3.4-WinVS2008_java/393/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 179891 lines...] [junit] 2013-12-30 09:30:15,486 [myid:] - INFO [main:FinalRequestProcessor@415] - shutdown of request processor complete [junit] 2013-12-30 09:30:15,487 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-12-30 09:30:15,728 [myid:] - INFO [main-SendThread(127.0.0.1:11221):ClientCnxn$SendThread@968] - Opening socket connection to server 127.0.0.1/127.0.0.1:11221. Will not attempt to authenticate using SASL (unknown error) [junit] 2013-12-30 09:30:16,476 [myid:] - INFO [main:JMXEnv@135] - ensureOnly:[] [junit] 2013-12-30 09:30:16,477 [myid:] - INFO [main:ClientBase@413] - STARTING server [junit] 2013-12-30 09:30:16,477 [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\test173821282786237.junit.dir\version-2 snapdir f:\hudson\hudson-slave\workspace\ZooKeeper-3.4-WinVS2008_java\branch-3.4\build\test\tmp\test173821282786237.junit.dir\version-2 [junit] 2013-12-30 09:30:16,479 [myid:] - INFO [main:NIOServerCnxnFactory@94] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2013-12-30 09:30:16,482 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-12-30 09:30:16,483 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@197] - Accepted socket connection from /127.0.0.1:64262 [junit] 2013-12-30 09:30:16,483 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing stat command from /127.0.0.1:64262 [junit] 2013-12-30 09:30:16,483 [myid:] - INFO [Thread-4:NIOServerCnxn$StatCommand@663] - Stat command output [junit] 2013-12-30 09:30:16,484 [myid:] - INFO [Thread-4:NIOServerCnxn@1007] - Closed socket connection for client /127.0.0.1:64262 (no session established for client) [junit] 2013-12-30 09:30:16,484 [myid:] - INFO [main:JMXEnv@135] - ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] 2013-12-30 09:30:16,485 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2013-12-30 09:30:16,485 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2013-12-30 09:30:16,485 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2013-12-30 09:30:16,486 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-12-30 09:30:16,488 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 10761 [junit] 2013-12-30 09:30:16,488 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 20 [junit] 2013-12-30 09:30:16,489 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota [junit] 2013-12-30 09:30:16,489 [myid:] - INFO [main:ClientBase@450] - tearDown starting [junit] 2013-12-30 09:30:16,723 [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] 2013-12-30 09:30:16,723 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@197] - Accepted socket connection from /127.0.0.1:64258 [junit] 2013-12-30 09:30:16,723 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:ZooKeeperServer@861] - Client attempting to renew session 0x14342d6dd23 at /127.0.0.1:64258 [junit] 2013-12-30 09:30:16,724 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:ZooKeeperServer@617] - Established session 0x14342d6dd23 with negotiated timeout 3 for client /127.0.0.1:64258 [junit] 2013-12-30 09:30:16,724 [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 = 0x14342d6dd23, negotiated timeout = 3 [junit] 2013-12-30 09:30:16,725 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@494] - Processed session termination for sessionid: 0x14342d6dd23 [junit] 2013-12-30 09:30:16,725 [myid:] - INFO [SyncThread:0:FileTxnLog@199] - Creating new log file: log.c [junit] 2013-12-30 09:30:16,735 [myid:] - INFO [main:ZooKeeper@684] - Session: 0x14342d6dd23 closed [junit] 2013-12-30 09:30:16,735 [myid:] - INFO [main:ClientBase@420] - STOPPING server [junit] 2013-12-30 09:30:16,735 [myid:] - WARN
[jira] [Commented] (ZOOKEEPER-102) Need to replace Jute with supported code
[ https://issues.apache.org/jira/browse/ZOOKEEPER-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858679#comment-13858679 ] Leader Ni commented on ZOOKEEPER-102: - So, how about avro now in hadoop，and any paln to replace jute? Need to replace Jute with supported code Key: ZOOKEEPER-102 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-102 Project: ZooKeeper Issue Type: Improvement Reporter: Benjamin Reed ZooKeeper currently uses Jute to serialize objects to put on the wire and on disk. We pulled Jute out of Hadoop and added a C binding. Both versions of Jute have evolved (although Hadoop still doesn't have a C binding). It would be nice to use a more standard serialization library. Some options include Thrift or Google's protocol buffers. Our main requirements would be Java and C bindings and good performance. (For example, serializing to XML would give us incredibly bad performance and would not be acceptible!) -- 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=13858680#comment-13858680
]
Flavio Junqueira commented on ZOOKEEPER-1833:
-
Makes sense, thanks for pointing it out! The tests that failed in build #393
are these, in the case anyone is interested in having a look and helping out:
{noformat}
TEST METHOD FAILED testHighestZxidJoinLate
TEST METHOD FAILED testUpdatingEpoch
TEST METHOD FAILED testAcls
TEST METHOD FAILED testHammerBasic
TEST METHOD FAILED testFourLetterWords
TEST METHOD FAILED testQuotaWithQuorum
{noformat}
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: 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
[jira] [Created] (ZOOKEEPER-1854) ClientBase ZooKeeper server clean-up
Germán Blanco created ZOOKEEPER-1854: Summary: ClientBase ZooKeeper server clean-up Key: ZOOKEEPER-1854 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1854 Project: ZooKeeper Issue Type: Sub-task Components: tests Affects Versions: 3.4.5, 3.5.0 Environment: Windows 7, Java 1.7 Reporter: Germán Blanco Assignee: Germán Blanco Fix For: 3.4.6, 3.5.0 The ClientBase utility for tests provides methods for creating a ZooKeeper server, however the close up methods don't seem to shutdown that ZooKeeper server. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
ZooKeeper-trunk-WinVS2008_java - Build # 639 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008_java/639/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 250254 lines...] [junit] 2013-12-30 09:55:33,000 [myid:] - INFO [SessionTracker:SessionTrackerImpl@134] - SessionTrackerImpl exited loop! [junit] 2013-12-30 09:55:33,001 [myid:] - INFO [SessionTracker:SessionTrackerImpl@134] - SessionTrackerImpl exited loop! [junit] 2013-12-30 09:55:33,074 [myid:] - INFO [main-SendThread(127.0.0.1:11221):ClientCnxn$SendThread@1008] - Opening socket connection to server 127.0.0.1/127.0.0.1:11221. Will not attempt to authenticate using SASL (unknown error) [junit] 2013-12-30 09:55:33,208 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[] [junit] 2013-12-30 09:55:33,209 [myid:] - INFO [main:ClientBase@414] - STARTING server [junit] 2013-12-30 09:55:33,209 [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\test625099667631270729.junit.dir\version-2 snapdir f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008_java\trunk\build\test\tmp\test625099667631270729.junit.dir\version-2 [junit] 2013-12-30 09:55:33,210 [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] 2013-12-30 09:55:33,211 [myid:] - INFO [main:NIOServerCnxnFactory@683] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2013-12-30 09:55:33,212 [myid:] - INFO [main:FileSnap@83] - Reading snapshot f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008_java\trunk\build\test\tmp\test625099667631270729.junit.dir\version-2\snapshot.b [junit] 2013-12-30 09:55:33,214 [myid:] - INFO [main:FileTxnSnapLog@297] - Snapshotting: 0xb to f:\hudson\hudson-slave\workspace\ZooKeeper-trunk-WinVS2008_java\trunk\build\test\tmp\test625099667631270729.junit.dir\version-2\snapshot.b [junit] 2013-12-30 09:55:33,216 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-12-30 09:55:33,217 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:50990 [junit] 2013-12-30 09:55:33,217 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@835] - Processing stat command from /127.0.0.1:50990 [junit] 2013-12-30 09:55:33,218 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn$StatCommand@684] - Stat command output [junit] 2013-12-30 09:55:33,218 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@1006] - Closed socket connection for client /127.0.0.1:50990 (no session established for client) [junit] 2013-12-30 09:55:33,218 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] 2013-12-30 09:55:33,220 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2013-12-30 09:55:33,220 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2013-12-30 09:55:33,220 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2013-12-30 09:55:33,220 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-12-30 09:55:33,220 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 13054 [junit] 2013-12-30 09:55:33,221 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 22 [junit] 2013-12-30 09:55:33,221 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota [junit] 2013-12-30 09:55:33,221 [myid:] - INFO [main:ClientBase@451] - tearDown starting [junit] 2013-12-30 09:55:33,563 [myid:] - INFO [main-SendThread(127.0.0.1:11221):ClientCnxn$SendThread@882] - Socket connection established to 127.0.0.1/127.0.0.1:11221, initiating session [junit] 2013-12-30 09:55:33,563 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:50985 [junit] 2013-12-30 09:55:33,564 [myid:] - INFO [NIOWorkerThread-2:ZooKeeperServer@858] - Client attempting to renew session 0x14342ee01cd at /127.0.0.1:50985 [junit] 2013-12-30 09:55:33,565 [myid:] - INFO [NIOWorkerThread-2:ZooKeeperServer@604] - Established session 0x14342ee01cd with negotiated timeout 3 for client /127.0.0.1:50985 [junit] 2013-12-30 09:55:33,565 [myid:] - INFO [main-SendThread(127.0.0.1:11221):ClientCnxn$SendThread@1261] - Session
[jira] [Updated] (ZOOKEEPER-1854) ClientBase ZooKeeper server clean-up
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Germán Blanco updated ZOOKEEPER-1854: - Attachment: ZOOKEEPER-1854-b3.4.patch ClientBase ZooKeeper server clean-up Key: ZOOKEEPER-1854 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1854 Project: ZooKeeper Issue Type: Sub-task Components: tests Affects Versions: 3.4.5, 3.5.0 Environment: Windows 7, Java 1.7 Reporter: Germán Blanco Assignee: Germán Blanco Fix For: 3.4.6, 3.5.0 Attachments: ZOOKEEPER-1854-b3.4.patch The ClientBase utility for tests provides methods for creating a ZooKeeper server, however the close up methods don't seem to shutdown that ZooKeeper server. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (ZOOKEEPER-1854) ClientBase ZooKeeper server clean-up
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Germán Blanco updated ZOOKEEPER-1854: - Attachment: ZOOKEEPER-1854.patch Please correct me if I am wrong, but I don't see this server being shutdown anywhere. I see the database being closed, and I don't know why that is done, but that is not the only thing that needs to be closed, right? ClientBase ZooKeeper server clean-up Key: ZOOKEEPER-1854 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1854 Project: ZooKeeper Issue Type: Sub-task Components: tests Affects Versions: 3.4.5, 3.5.0 Environment: Windows 7, Java 1.7 Reporter: Germán Blanco Assignee: Germán Blanco Fix For: 3.4.6, 3.5.0 Attachments: ZOOKEEPER-1854-b3.4.patch, ZOOKEEPER-1854.patch The ClientBase utility for tests provides methods for creating a ZooKeeper server, however the close up methods don't seem to shutdown that ZooKeeper server. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
ZooKeeper-trunk-jdk7 - Build # 741 - Failure
See https://builds.apache.org/job/ZooKeeper-trunk-jdk7/741/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 206963 lines...] [junit] 2013-12-30 10:18:14,340 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@156] - PrepRequestProcessor exited loop! [junit] 2013-12-30 10:18:14,340 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@168] - SyncRequestProcessor exited! [junit] 2013-12-30 10:18:14,341 [myid:] - INFO [main:FinalRequestProcessor@442] - shutdown of request processor complete [junit] 2013-12-30 10:18:14,341 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-12-30 10:18:14,342 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[] [junit] 2013-12-30 10:18:14,344 [myid:] - INFO [main:ClientBase@414] - STARTING server [junit] 2013-12-30 10:18:14,344 [myid:] - INFO [main:ZooKeeperServer@149] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk7/trunk/build/test/tmp/test6757438650396793087.junit.dir/version-2 snapdir /x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk7/trunk/build/test/tmp/test6757438650396793087.junit.dir/version-2 [junit] 2013-12-30 10:18:14,344 [myid:] - INFO [main:NIOServerCnxnFactory@670] - Configuring NIO connection handler with 10s sessionless connection timeout, 3 selector thread(s), 48 worker threads, and 64 kB direct buffers. [junit] 2013-12-30 10:18:14,345 [myid:] - INFO [main:NIOServerCnxnFactory@683] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2013-12-30 10:18:14,346 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk7/trunk/build/test/tmp/test6757438650396793087.junit.dir/version-2/snapshot.b [junit] 2013-12-30 10:18:14,349 [myid:] - INFO [main:FileTxnSnapLog@297] - Snapshotting: 0xb to /x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk7/trunk/build/test/tmp/test6757438650396793087.junit.dir/version-2/snapshot.b [junit] 2013-12-30 10:18:14,351 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-12-30 10:18:14,352 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296] - Accepted socket connection from /127.0.0.1:45340 [junit] 2013-12-30 10:18:14,353 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@835] - Processing stat command from /127.0.0.1:45340 [junit] 2013-12-30 10:18:14,353 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn$StatCommand@684] - Stat command output [junit] 2013-12-30 10:18:14,354 [myid:] - INFO [NIOWorkerThread-1:NIOServerCnxn@1006] - Closed socket connection for client /127.0.0.1:45340 (no session established for client) [junit] 2013-12-30 10:18:14,354 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] 2013-12-30 10:18:14,356 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2013-12-30 10:18:14,356 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2013-12-30 10:18:14,356 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2013-12-30 10:18:14,357 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-12-30 10:18:14,357 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 18198 [junit] 2013-12-30 10:18:14,357 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 25 [junit] 2013-12-30 10:18:14,358 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota [junit] 2013-12-30 10:18:14,358 [myid:] - INFO [main:ClientBase@451] - tearDown starting [junit] 2013-12-30 10:18:14,410 [myid:] - INFO [main:ZooKeeper@777] - Session: 0x1434302cd95 closed [junit] 2013-12-30 10:18:14,411 [myid:] - INFO [main:ClientBase@421] - STOPPING server [junit] 2013-12-30 10:18:14,410 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down [junit] 2013-12-30 10:18:14,411 [myid:] - INFO [ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - ConnnectionExpirerThread interrupted [junit] 2013-12-30 10:18:14,411 [myid:] - INFO [NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@219] - accept thread exitted run method [junit] 2013-12-30 10:18:14,421 [myid:] - INFO [NIOServerCxnFactory.SelectorThread-2:NIOServerCnxnFactory$SelectorThread@420] - selector thread exitted run method [junit] 2013-12-30 10:18:14,411 [myid:] - INFO
ZooKeeper_branch34_jdk7 - Build # 430 - Failure
See https://builds.apache.org/job/ZooKeeper_branch34_jdk7/430/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 410 lines...] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS /repos/asf/zookeeper/branches/branch-3.4 failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:388) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.getRevisionNumber(SVNBasicDelegate.java:480) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.getLocations(SVNBasicDelegate.java:833) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.createRepository(SVNBasicDelegate.java:527) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doCheckout(SVNUpdateClient16.java:875) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:19) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:8) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:777) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:99) ... 17 more Caused by: svn: E175002: OPTIONS /repos/asf/zookeeper/branches/branch-3.4 failed at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97) ... 36 more Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS request failed on '/repos/asf/zookeeper/branches/branch-3.4' svn: E175002: timed out waiting for server at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:777) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 35 more Caused by: svn: E175002: OPTIONS request failed on '/repos/asf/zookeeper/branches/branch-3.4' at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:775) ... 36 more Caused by: svn: E175002: timed out waiting for server at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:514) ... 36 more Caused by: java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:327) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:193) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:180) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:385) at java.net.Socket.connect(Socket.java:546) at org.tmatesoft.svn.core.internal.util.SVNSocketConnection.run(SVNSocketConnection.java:57) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) ... 5 more Recording test results Email was triggered for: Failure Sending email for
ZooKeeper_branch34_openjdk7 - Build # 420 - Failure
See https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/420/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 410 lines...] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS /repos/asf/zookeeper/branches/branch-3.4 failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:388) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.getRevisionNumber(SVNBasicDelegate.java:480) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.getLocations(SVNBasicDelegate.java:833) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.createRepository(SVNBasicDelegate.java:527) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doCheckout(SVNUpdateClient16.java:875) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:19) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:8) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:777) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:99) ... 17 more Caused by: svn: E175002: OPTIONS /repos/asf/zookeeper/branches/branch-3.4 failed at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97) ... 36 more Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS request failed on '/repos/asf/zookeeper/branches/branch-3.4' svn: E175002: timed out waiting for server at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:777) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 35 more Caused by: svn: E175002: OPTIONS request failed on '/repos/asf/zookeeper/branches/branch-3.4' at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:775) ... 36 more Caused by: svn: E175002: timed out waiting for server at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:514) ... 36 more Caused by: java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:327) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:193) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:180) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:385) at java.net.Socket.connect(Socket.java:546) at org.tmatesoft.svn.core.internal.util.SVNSocketConnection.run(SVNSocketConnection.java:57) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) ... 5 more Recording test results Email was triggered for: Failure Sending email for
[jira] [Commented] (ZOOKEEPER-1854) ClientBase ZooKeeper server clean-up
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858696#comment-13858696 ] Rakesh R commented on ZOOKEEPER-1854: - Hi German, Please see factory#shutdown logic, here I could see zkServer#shutdown and I feel there is no need of explicit zks#shutdown. Am I missing anything?. It would be great if you can look at ZOOKEEPER-1852, there I mentioned one case of missing server shutdown and will affect other test cases. ClientBase ZooKeeper server clean-up Key: ZOOKEEPER-1854 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1854 Project: ZooKeeper Issue Type: Sub-task Components: tests Affects Versions: 3.4.5, 3.5.0 Environment: Windows 7, Java 1.7 Reporter: Germán Blanco Assignee: Germán Blanco Fix For: 3.4.6, 3.5.0 Attachments: ZOOKEEPER-1854-b3.4.patch, ZOOKEEPER-1854.patch The ClientBase utility for tests provides methods for creating a ZooKeeper server, however the close up methods don't seem to shutdown that ZooKeeper server. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (ZOOKEEPER-1854) ClientBase ZooKeeper server clean-up
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858701#comment-13858701 ] Hadoop QA commented on ZOOKEEPER-1854: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12620825/ZOOKEEPER-1854.patch against trunk revision 1553693. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1868//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1868//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1868//console This message is automatically generated. ClientBase ZooKeeper server clean-up Key: ZOOKEEPER-1854 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1854 Project: ZooKeeper Issue Type: Sub-task Components: tests Affects Versions: 3.4.5, 3.5.0 Environment: Windows 7, Java 1.7 Reporter: Germán Blanco Assignee: Germán Blanco Fix For: 3.4.6, 3.5.0 Attachments: ZOOKEEPER-1854-b3.4.patch, ZOOKEEPER-1854.patch The ClientBase utility for tests provides methods for creating a ZooKeeper server, however the close up methods don't seem to shutdown that ZooKeeper server. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Failed: ZOOKEEPER-1854 PreCommit Build #1868
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1854 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1868/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 237494 lines...] [exec] [exec] [exec] [exec] -1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12620825/ZOOKEEPER-1854.patch [exec] against trunk revision 1553693. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 3 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [exec] -1 core tests. The patch failed core unit tests. [exec] [exec] +1 contrib tests. The patch passed contrib unit tests. [exec] [exec] Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1868//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1868//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1868//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] 539338496e6cb757fd3508d1d47ac95f49354137 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: 33 minutes 3 seconds Build step 'Execute shell' marked build as failure Archiving artifacts Recording test results Description set: ZOOKEEPER-1854 Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## All tests passed
ZooKeeper-trunk - Build # 2170 - Failure
See https://builds.apache.org/job/ZooKeeper-trunk/2170/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 293567 lines...] [exec] Log Message Received: [2013-12-30 11:04:35,130:23636(0x2b5dda82eda0):ZOO_INFO@log_env@922: Client environment:os.version=#71-Ubuntu SMP Wed Jul 20 17:42:25 UTC 2011] [exec] Log Message Received: [2013-12-30 11:04:35,130:23636(0x2b5dda82eda0):ZOO_INFO@log_env@930: Client environment:user.name=(null)] [exec] Log Message Received: [2013-12-30 11:04:35,130:23636(0x2b5dda82eda0):ZOO_INFO@log_env@938: Client environment:user.home=/home/jenkins] [exec] Log Message Received: [2013-12-30 11:04:35,130:23636(0x2b5dda82eda0):ZOO_INFO@log_env@950: Client environment:user.dir=/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/test/test-cppunit] [exec] Log Message Received: [2013-12-30 11:04:35,130:23636(0x2b5dda82eda0):ZOO_INFO@zookeeper_init_internal@993: Initiating client connection, host=127.0.0.1:22181 sessionTimeout=1 watcher=0x4422e0 sessionId=0 sessionPasswd=null context=0x7fff8173d740 flags=0] [exec] Log Message Received: [2013-12-30 11:04:35,131:23636(0x2b5ddbc8e700):ZOO_INFO@check_events@2090: initiated connection to server [127.0.0.1:22181]] [exec] Log Message Received: [2013-12-30 11:04:35,140:23636(0x2b5ddbc8e700):ZOO_INFO@check_events@2138: session establishment complete on server [127.0.0.1:22181], sessionId=0x143432c93dd000e, negotiated timeout=1] [exec] : elapsed 1001 : OK [exec] Zookeeper_simpleSystem::testAsyncWatcherAutoReset ZooKeeper server started : elapsed 9757 : OK [exec] Zookeeper_simpleSystem::testDeserializeString : elapsed 0 : OK [exec] Zookeeper_simpleSystem::testNullData : elapsed 1027 : OK [exec] Zookeeper_simpleSystem::testIPV6 : elapsed 1007 : OK [exec] Zookeeper_simpleSystem::testCreate : elapsed 1017 : OK [exec] Zookeeper_simpleSystem::testPath : elapsed 1020 : OK [exec] Zookeeper_simpleSystem::testPathValidation : elapsed 1035 : OK [exec] Zookeeper_simpleSystem::testPing : elapsed 17450 : OK [exec] Zookeeper_simpleSystem::testAcl : elapsed 1036 : OK [exec] Zookeeper_simpleSystem::testChroot : elapsed 4042 : OK [exec] Zookeeper_simpleSystem::testAuth ZooKeeper server started ZooKeeper server started : elapsed 29565 : OK [exec] Zookeeper_simpleSystem::testHangingClient : elapsed 1032 : OK [exec] Zookeeper_simpleSystem::testWatcherAutoResetWithGlobal ZooKeeper server started ZooKeeper server started ZooKeeper server started : elapsed 13428 : OK [exec] Zookeeper_simpleSystem::testWatcherAutoResetWithLocal ZooKeeper server started ZooKeeper server started ZooKeeper server started : elapsed 14494 : OK [exec] Zookeeper_simpleSystem::testGetChildren2 : elapsed 1055 : OK [exec] Zookeeper_simpleSystem::testLastZxid : elapsed 2519 : OK [exec] Zookeeper_watchers::testDefaultSessionWatcher1 : elapsed 52 : OK [exec] Zookeeper_watchers::testDefaultSessionWatcher2 : elapsed 4 : OK [exec] Zookeeper_watchers::testObjectSessionWatcher1 : elapsed 54 : OK [exec] Zookeeper_watchers::testObjectSessionWatcher2 : elapsed 56 : OK [exec] Zookeeper_watchers::testNodeWatcher1 : elapsed 56 : OK [exec] Zookeeper_watchers::testChildWatcher1 : elapsed 104 : OK [exec] Zookeeper_watchers::testChildWatcher2 : elapsed 54 : OK [exec] /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/src/c/tests/TestReconfig.cc:183: Assertion: equality assertion failed [Expected: 1, Actual : 0] [exec] /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/src/c/tests/TestReconfig.cc:473: Assertion: assertion failed [Expression: found != string::npos] [exec] Failures !!! [exec] Run: 69 Failure total: 2 Failures: 2 Errors: 0 [exec] FAIL: zktest-mt [exec] == [exec] 1 of 2 tests failed [exec] Please report to u...@zookeeper.apache.org [exec] == [exec] make[1]: *** [check-TESTS] Error 1 [exec] make[1]: Leaving directory `/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build/test/test-cppunit' [exec] make: *** [check-am] Error 2 BUILD FAILED /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build.xml:1404: The following error occurred while executing this line: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build.xml:1364: The following error occurred while executing this line: /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/build.xml:1374: exec returned: 2 Total time: 31 minutes 48 seconds Build step 'Execute shell' marked build as failure [FINDBUGS] Skipping publisher since build result is FAILURE [WARNINGS] Skipping publisher since build result is FAILURE Archiving
[jira] [Commented] (ZOOKEEPER-1854) ClientBase ZooKeeper server clean-up
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858722#comment-13858722 ] Flavio Junqueira commented on ZOOKEEPER-1854: - When some question is raised, please cancel the patch so that we don't end up committing patches before reaching agreement. The patch proposer isn't going to be offended (or at least shouldn't be), it is just a way of signalling that something is still not clear. ClientBase ZooKeeper server clean-up Key: ZOOKEEPER-1854 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1854 Project: ZooKeeper Issue Type: Sub-task Components: tests Affects Versions: 3.4.5, 3.5.0 Environment: Windows 7, Java 1.7 Reporter: Germán Blanco Assignee: Germán Blanco Fix For: 3.4.6, 3.5.0 Attachments: ZOOKEEPER-1854-b3.4.patch, ZOOKEEPER-1854.patch The ClientBase utility for tests provides methods for creating a ZooKeeper server, however the close up methods don't seem to shutdown that ZooKeeper server. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (ZOOKEEPER-1854) ClientBase ZooKeeper server clean-up
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Germán Blanco resolved ZOOKEEPER-1854. -- Resolution: Invalid I wonder how I missed that. This JIRA doesn't make sense. ClientBase ZooKeeper server clean-up Key: ZOOKEEPER-1854 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1854 Project: ZooKeeper Issue Type: Sub-task Components: tests Affects Versions: 3.4.5, 3.5.0 Environment: Windows 7, Java 1.7 Reporter: Germán Blanco Assignee: Germán Blanco Fix For: 3.4.6, 3.5.0 Attachments: ZOOKEEPER-1854-b3.4.patch, ZOOKEEPER-1854.patch The ClientBase utility for tests provides methods for creating a ZooKeeper server, however the close up methods don't seem to shutdown that ZooKeeper server. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (ZOOKEEPER-1854) ClientBase ZooKeeper server clean-up
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858730#comment-13858730 ] Flavio Junqueira commented on ZOOKEEPER-1854: - Perhaps my logic is backwards but it seems to me that the server should be shutting down the cnxn server, not the other way around. This is just a digression, such a refactoring is out of the scope of this jira. ClientBase ZooKeeper server clean-up Key: ZOOKEEPER-1854 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1854 Project: ZooKeeper Issue Type: Sub-task Components: tests Affects Versions: 3.4.5, 3.5.0 Environment: Windows 7, Java 1.7 Reporter: Germán Blanco Assignee: Germán Blanco Fix For: 3.4.6, 3.5.0 Attachments: ZOOKEEPER-1854-b3.4.patch, ZOOKEEPER-1854.patch The ClientBase utility for tests provides methods for creating a ZooKeeper server, however the close up methods don't seem to shutdown that ZooKeeper server. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (ZOOKEEPER-1852) ServerCnxnFactory instance is not properly cleanedup
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858731#comment-13858731
]
Germán Blanco commented on ZOOKEEPER-1852:
--
So what happens now when createNewServerInstance fails and null is returned?
Apparently the startServerInstance is called and it fails with
NullPointerException, is that intended?
ServerCnxnFactory instance is not properly cleanedup
Key: ZOOKEEPER-1852
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1852
Project: ZooKeeper
Issue Type: Sub-task
Components: tests
Reporter: Rakesh R
Assignee: Rakesh R
Fix For: 3.4.6, 3.5.0
Attachments: ZOOKEEPER-1852-br-3.4.patch,
ZOOKEEPER-1852-br-3.4.patch, ZOOKEEPER-1852.patch, ZOOKEEPER-1852.patch
ClientBase#createNewServerInstance() - Say the startup of the server fails,
this will not initialize 'serverFactory' and will be null. When the flow
comes to teardown/shutdown, it will bypass stopping of this server instance
due to the following check. This will affect other test case verifications
like, jmx check 'JMXEnv#ensureOnly'.
ClientBase#shutdownServerInstance
{code}
static void shutdownServerInstance(ServerCnxnFactory factory,
String hostPort)
{
if (factory != null) {
//...shutdown logic
}
{code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (ZOOKEEPER-1852) ServerCnxnFactory instance is not properly cleanedup
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858742#comment-13858742
]
Rakesh R commented on ZOOKEEPER-1852:
-
Hi German,
{quote}So what happens now when createNewServerInstance fails and null is
returned?
Apparently the startServerInstance is called and it fails with
NullPointerException, is that intended?{quote}
In my patch createNewServerInstance method call, will just instantiate
'factory' and return it. I think there wont be any case of returning null
silently from the following code, if there is an exception it will throw back
to the caller, isn't it?
{code}
factory = ServerCnxnFactory.createFactory(PORT, maxCnxns);
{code}
ServerCnxnFactory instance is not properly cleanedup
Key: ZOOKEEPER-1852
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1852
Project: ZooKeeper
Issue Type: Sub-task
Components: tests
Reporter: Rakesh R
Assignee: Rakesh R
Fix For: 3.4.6, 3.5.0
Attachments: ZOOKEEPER-1852-br-3.4.patch,
ZOOKEEPER-1852-br-3.4.patch, ZOOKEEPER-1852.patch, ZOOKEEPER-1852.patch
ClientBase#createNewServerInstance() - Say the startup of the server fails,
this will not initialize 'serverFactory' and will be null. When the flow
comes to teardown/shutdown, it will bypass stopping of this server instance
due to the following check. This will affect other test case verifications
like, jmx check 'JMXEnv#ensureOnly'.
ClientBase#shutdownServerInstance
{code}
static void shutdownServerInstance(ServerCnxnFactory factory,
String hostPort)
{
if (factory != null) {
//...shutdown logic
}
{code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (ZOOKEEPER-1852) ServerCnxnFactory instance is not properly cleanedup
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858750#comment-13858750
]
Rakesh R commented on ZOOKEEPER-1852:
-
For more understanding about the scenario, I'm adding few more information.
Please see it.
The case what I have observed in the build is, say one of the test case failed
at waiting for server up as shown below. Now in this case
'ClientBase.serverFactory' reference will not be initialized and teardown will
not be able to shutdown this server. This will leave server running and
affecting other test cases. Example log pattern has been taken from
https://builds.apache.org/job/ZooKeeper-3.4-WinVS2008_java/390/
{code}
[junit] 2013-12-25 09:08:00,837 [myid:] - INFO
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@62] - TEST METHOD FAILED
testWatchAutoResetWithPending
[junit] java.lang.AssertionError: waiting for server up
[junit] at org.junit.Assert.fail(Assert.java:91)
[junit] at org.junit.Assert.assertTrue(Assert.java:43)
[junit] at
org.apache.zookeeper.test.ClientBase.createNewServerInstance(ClientBase.java:337)
[junit] at
org.apache.zookeeper.test.ClientBase.startServer(ClientBase.java:414)
[junit] at
org.apache.zookeeper.test.WatcherTest.testWatchAutoResetWithPending(WatcherTest.java:208)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
{code}
Following log showing the test case is failing by seeing unexpected beans which
was left open in previous test case.
{code}
[junit] 2013-12-25 09:08:06,018 [myid:] - INFO [main:JMXEnv@142] -
unexpected:org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=Connections,name2=127.0.0.1,name3=0x1432900e409
[junit] 2013-12-25 09:08:06,018 [myid:] - INFO [main:JMXEnv@142] -
unexpected:org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree
[junit] 2013-12-25 09:08:06,018 [myid:] - INFO [main:JMXEnv@142] -
unexpected:org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=Connections,name2=127.0.0.1,name3=0x1432900e4090002
[junit] 2013-12-25 09:08:06,018 [myid:] - INFO [main:JMXEnv@142] -
unexpected:org.apache.ZooKeeperService:name0=StandaloneServer_port-1
[junit] 2013-12-25 09:08:06,018 [myid:] - INFO [main:ZKTestCase$1@65] -
FAILED testWatchAutoResetWithPending
[junit] org.junit.internal.runners.model.MultipleFailureException
[junit] at
org.junit.internal.runners.model.MultipleFailureException.assertEmpty(MultipleFailureException.java:23)
[junit] at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:42)
[junit] at org.junit.rules.TestWatchman$1.evaluate(TestWatchman.java:48)
[junit] at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
{code}
ServerCnxnFactory instance is not properly cleanedup
Key: ZOOKEEPER-1852
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1852
Project: ZooKeeper
Issue Type: Sub-task
Components: tests
Reporter: Rakesh R
Assignee: Rakesh R
Fix For: 3.4.6, 3.5.0
Attachments: ZOOKEEPER-1852-br-3.4.patch,
ZOOKEEPER-1852-br-3.4.patch, ZOOKEEPER-1852.patch, ZOOKEEPER-1852.patch
ClientBase#createNewServerInstance() - Say the startup of the server fails,
this will not initialize 'serverFactory' and will be null. When the flow
comes to teardown/shutdown, it will bypass stopping of this server instance
due to the following check. This will affect other test case verifications
like, jmx check 'JMXEnv#ensureOnly'.
ClientBase#shutdownServerInstance
{code}
static void shutdownServerInstance(ServerCnxnFactory factory,
String hostPort)
{
if (factory != null) {
//...shutdown logic
}
{code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (ZOOKEEPER-1852) ServerCnxnFactory instance is not properly cleanedup
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858861#comment-13858861
]
Germán Blanco commented on ZOOKEEPER-1852:
--
So this is covering a problem when TruncateTest fails and that leaves a running
server that affects additional test cases later on, right?
I see now the goal, thank you for explaining.
+1
Would you mind taking a look at the patch (wrongly) in ZOOKEEPER-1833?
I didn't put it in a subtask by mistake, and I don't know if it makes sense to
do it now.
Anyway, I believe it solves a problem of a run-away server like this one, but
one that runs away in all cases (failure or success).
ServerCnxnFactory instance is not properly cleanedup
Key: ZOOKEEPER-1852
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1852
Project: ZooKeeper
Issue Type: Sub-task
Components: tests
Reporter: Rakesh R
Assignee: Rakesh R
Fix For: 3.4.6, 3.5.0
Attachments: ZOOKEEPER-1852-br-3.4.patch,
ZOOKEEPER-1852-br-3.4.patch, ZOOKEEPER-1852.patch, ZOOKEEPER-1852.patch
ClientBase#createNewServerInstance() - Say the startup of the server fails,
this will not initialize 'serverFactory' and will be null. When the flow
comes to teardown/shutdown, it will bypass stopping of this server instance
due to the following check. This will affect other test case verifications
like, jmx check 'JMXEnv#ensureOnly'.
ClientBase#shutdownServerInstance
{code}
static void shutdownServerInstance(ServerCnxnFactory factory,
String hostPort)
{
if (factory != null) {
//...shutdown logic
}
{code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (ZOOKEEPER-102) Need to replace Jute with supported code
[ https://issues.apache.org/jira/browse/ZOOKEEPER-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858886#comment-13858886 ] Germán Blanco commented on ZOOKEEPER-102: - Ooops, should have read the entire thread ... so maybe there could be ways to enable the upgrade after all. Need to replace Jute with supported code Key: ZOOKEEPER-102 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-102 Project: ZooKeeper Issue Type: Improvement Reporter: Benjamin Reed ZooKeeper currently uses Jute to serialize objects to put on the wire and on disk. We pulled Jute out of Hadoop and added a C binding. Both versions of Jute have evolved (although Hadoop still doesn't have a C binding). It would be nice to use a more standard serialization library. Some options include Thrift or Google's protocol buffers. Our main requirements would be Java and C bindings and good performance. (For example, serializing to XML would give us incredibly bad performance and would not be acceptible!) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (ZOOKEEPER-1852) ServerCnxnFactory instance is not properly cleanedup
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858961#comment-13858961
]
Rakesh R commented on ZOOKEEPER-1852:
-
Yeah, +1 creating a subtask for PrepRequestProcessorTest cleanup and good to
correct it, as run-away server may affect other testcases.
ServerCnxnFactory instance is not properly cleanedup
Key: ZOOKEEPER-1852
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1852
Project: ZooKeeper
Issue Type: Sub-task
Components: tests
Reporter: Rakesh R
Assignee: Rakesh R
Fix For: 3.4.6, 3.5.0
Attachments: ZOOKEEPER-1852-br-3.4.patch,
ZOOKEEPER-1852-br-3.4.patch, ZOOKEEPER-1852.patch, ZOOKEEPER-1852.patch
ClientBase#createNewServerInstance() - Say the startup of the server fails,
this will not initialize 'serverFactory' and will be null. When the flow
comes to teardown/shutdown, it will bypass stopping of this server instance
due to the following check. This will affect other test case verifications
like, jmx check 'JMXEnv#ensureOnly'.
ClientBase#shutdownServerInstance
{code}
static void shutdownServerInstance(ServerCnxnFactory factory,
String hostPort)
{
if (factory != null) {
//...shutdown logic
}
{code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
ZooKeeper_branch33_solaris - Build # 753 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch33_solaris/753/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 98966 lines...] [junit] 2013-12-31 07:04:15,791 - INFO [main:ZooKeeperServer@154] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch33_solaris/trunk/build/test/tmp/test7698282616389788280.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch33_solaris/trunk/build/test/tmp/test7698282616389788280.junit.dir/version-2 [junit] 2013-12-31 07:04:15,792 - INFO [main:NIOServerCnxn$Factory@143] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2013-12-31 07:04:15,794 - INFO [main:FileSnap@82] - Reading snapshot /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch33_solaris/trunk/build/test/tmp/test7698282616389788280.junit.dir/version-2/snapshot.0 [junit] 2013-12-31 07:04:15,797 - INFO [main:FileTxnSnapLog@256] - Snapshotting: b [junit] 2013-12-31 07:04:15,800 - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-12-31 07:04:15,801 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn$Factory@251] - Accepted socket connection from /127.0.0.1:41191 [junit] 2013-12-31 07:04:15,802 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@1237] - Processing stat command from /127.0.0.1:41191 [junit] 2013-12-31 07:04:15,803 - INFO [Thread-4:NIOServerCnxn$StatCommand@1153] - Stat command output [junit] 2013-12-31 07:04:15,803 - INFO [Thread-4:NIOServerCnxn@1435] - Closed socket connection for client /127.0.0.1:41191 (no session established for client) [junit] ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] expect:InMemoryDataTree [junit] found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] expect:StandaloneServer_port [junit] found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-12-31 07:04:15,805 - INFO [main:ClientBase@408] - STOPPING server [junit] 2013-12-31 07:04:15,807 - INFO [ProcessThread:-1:PrepRequestProcessor@128] - PrepRequestProcessor exited loop! [junit] 2013-12-31 07:04:15,807 - INFO [SyncThread:0:SyncRequestProcessor@151] - SyncRequestProcessor exited! [junit] 2013-12-31 07:04:15,807 - INFO [main:FinalRequestProcessor@370] - shutdown of request processor complete [junit] 2013-12-31 07:04:15,809 - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] ensureOnly:[] [junit] 2013-12-31 07:04:15,810 - INFO [main:ClientBase@401] - STARTING server [junit] 2013-12-31 07:04:15,811 - INFO [main:ZooKeeperServer@154] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch33_solaris/trunk/build/test/tmp/test7698282616389788280.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch33_solaris/trunk/build/test/tmp/test7698282616389788280.junit.dir/version-2 [junit] 2013-12-31 07:04:15,812 - INFO [main:NIOServerCnxn$Factory@143] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2013-12-31 07:04:15,813 - INFO [main:FileSnap@82] - Reading snapshot /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch33_solaris/trunk/build/test/tmp/test7698282616389788280.junit.dir/version-2/snapshot.b [junit] 2013-12-31 07:04:15,815 - INFO [main:FileTxnSnapLog@256] - Snapshotting: b [junit] 2013-12-31 07:04:15,817 - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2013-12-31 07:04:15,818 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn$Factory@251] - Accepted socket connection from /127.0.0.1:41193 [junit] 2013-12-31 07:04:15,819 - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@1237] - Processing stat command from /127.0.0.1:41193 [junit] 2013-12-31 07:04:15,820 - INFO [Thread-5:NIOServerCnxn$StatCommand@1153] - Stat command output [junit] 2013-12-31 07:04:15,820 - INFO [Thread-5:NIOServerCnxn@1435] - Closed socket connection for client /127.0.0.1:41193 (no session established for client) [junit] ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] expect:InMemoryDataTree [junit] found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] expect:StandaloneServer_port [junit] found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2013-12-31 07:04:15,823 - INFO
Build failed in Jenkins: bookkeeper-trunk #489
See https://builds.apache.org/job/bookkeeper-trunk/489/ -- [...truncated 436 lines...] [INFO] Changes detected - recompiling the module! [INFO] Compiling 6 source files to https://builds.apache.org/job/bookkeeper-trunk/ws/hedwig-protocol/target/classes [INFO] [INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) @ hedwig-protocol --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/bookkeeper-trunk/ws/hedwig-protocol/src/test/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.0:testCompile (default-testCompile) @ hedwig-protocol --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.9:test (default-test) @ hedwig-protocol --- [INFO] Surefire report directory: https://builds.apache.org/job/bookkeeper-trunk/ws/hedwig-protocol/target/surefire-reports --- T E S T S --- --- T E S T S --- Results : Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ hedwig-protocol --- [INFO] Building jar: https://builds.apache.org/job/bookkeeper-trunk/ws/hedwig-protocol/target/hedwig-protocol-4.3.0-SNAPSHOT.jar [INFO] [INFO] findbugs-maven-plugin:2.5.2:check (default-cli) @ hedwig-protocol [INFO] [INFO] --- findbugs-maven-plugin:2.5.2:findbugs (findbugs) @ hedwig-protocol --- [INFO] Fork Value is true [INFO] Done FindBugs Analysis [INFO] [INFO] findbugs-maven-plugin:2.5.2:check (default-cli) @ hedwig-protocol [INFO] [INFO] --- findbugs-maven-plugin:2.5.2:check (default-cli) @ hedwig-protocol --- [INFO] BugInstance size is 0 [INFO] Error size is 0 [INFO] No errors/warnings found [INFO] [INFO] [INFO] Building bookkeeper-server 4.3.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bookkeeper-server --- [INFO] [INFO] --- apache-rat-plugin:0.7:check (default-cli) @ bookkeeper-server --- [INFO] Exclude: **/DataFormats.java [INFO] [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ bookkeeper-server --- [INFO] [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ bookkeeper-server --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 3 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ bookkeeper-server --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 159 source files to https://builds.apache.org/job/bookkeeper-trunk/ws/bookkeeper-server/target/classes [INFO] [INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) @ bookkeeper-server --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.0:testCompile (default-testCompile) @ bookkeeper-server --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 79 source files to https://builds.apache.org/job/bookkeeper-trunk/ws/bookkeeper-server/target/test-classes [INFO] [INFO] --- maven-surefire-plugin:2.9:test (default-test) @ bookkeeper-server --- [INFO] Surefire report directory: https://builds.apache.org/job/bookkeeper-trunk/ws/bookkeeper-server/target/surefire-reports --- T E S T S --- --- T E S T S --- Running org.apache.bookkeeper.replication.AutoRecoveryMainTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.3 sec Running org.apache.bookkeeper.replication.BookieAutoRecoveryTest Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 28.838 sec Running org.apache.bookkeeper.replication.BookieLedgerIndexTest Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.092 sec Running org.apache.bookkeeper.replication.AuditorPeriodicCheckTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.831 sec Running org.apache.bookkeeper.replication.AuditorLedgerCheckerTest Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 24.397 sec Running org.apache.bookkeeper.replication.TestLedgerUnderreplicationManager Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 18.102 sec Running org.apache.bookkeeper.replication.AuditorBookieTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.495 sec
Fwd: Build failed in Jenkins: bookkeeper-trunk #489
I was wondering if there is a jira open for the test that failed below, does anyone know? -Flavio Begin forwarded message: Tests in error: testWithMultipleBookieFailuresInLastEnsemble[2](org.apache.bookkeeper.client.BookieWriteLedgerTest)
RE: Build failed in Jenkins: bookkeeper-trunk #489
Hi Flavio, As test case name says, it is testing multiple bookie failures. On bookiefailure, when doing the ensemble reformation, unfortunately it is failing to connect to the Bookie-15039. But it should suppose to get connected and continue write operation. This is the reason for the test case failure. Please see the following log pattern: 2013-12-30 12:29:36,731 - INFO - [BookKeeperClientWorker-0-0:PerChannelBookieClient@167] - Connecting to bookie: /67.195.138.30:15039 2013-12-30 12:29:36,732 - ERROR - [New I/O client boss #5-1:PerChannelBookieClient$1@203] - Could not connect to bookie: [id: 0x019a639b, /229.27.250.246:46509 : /67.195.138.30:15039], current state CONNECTING 2013-12-30 12:29:36,732 - WARN - [BookKeeperClientWorker-0-0:PendingAddOp@158] - Write did not succeed: L0 E100 on /67.195.138.30:15039 2013-12-30 12:29:36,733 - INFO - [BookKeeperClientWorker-0-0:LedgerHandle@659] - Handling failure of bookie: /67.195.138.30:15039 index: 2 2013-12-30 12:29:36,733 - WARN - [BookKeeperClientWorker-0-0:RackawareEnsemblePlacementPolicy@491] - Failed to choose a bookie from /default-rack : excluded [Bookie:67.195.138.30:15036, Bookie:67.195.138.30:15038, Bookie:67.195.138.30:15039, Bookie:67.195.138.30:15040, Bookie:67.195.138.30:15035], fallback to choose bookie randomly from the cluster. I'm thinking, there could be chance of small network fluctuations or slow machine and resulting in connection failure. To handle this IMHO, we should have netty client connection timeout in place and should retry for few intervals. Let me do a try with bootstrap.setOption(connectTimeoutMillis, timeoutvalue); Shall I raise a JIRA to discuss about these concerns and will reach to a conclusion. Whats your opinion? -Rakesh -Original Message- From: Flavio Junqueira [mailto:fpjunque...@yahoo.com] Sent: 31 December 2013 01:51 To: bookkeeper-dev@zookeeper.apache.org Subject: Fwd: Build failed in Jenkins: bookkeeper-trunk #489 I was wondering if there is a jira open for the test that failed below, does anyone know? -Flavio Begin forwarded message: Tests in error: testWithMultipleBookieFailuresInLastEnsemble[2](org.apache.bookkeeper.client.BookieWriteLedgerTest)
Re: Build failed in Jenkins: bookkeeper-trunk #489
I don't think its connect timeout setting issue. as by default, netty channel connect timeout is 10 sec ( https://github.com/netty/netty/blob/3.2/src/main/java/org/jboss/netty/channel/DefaultChannelConfig.java#L38). If you checked the log, the log statements show that the connect operation is in same second. 2013-12-30 12:29:36,731 - INFO - [BookKeeperClientWorker-0-0:PerChannelBookieClient@167] - Connecting to bookie: /67.195.138.30:15039 2013-12-30 12:29:36,732 - ERROR - [New I/O client boss #5-1:PerChannelBookieClient$1@203] - Could not connect to bookie: [id: 0x019a639b, /229.27.250.246:46509 : /67.195.138.30:15039], current state CONNECTING On Mon, Dec 30, 2013 at 9:31 PM, Rakesh R rake...@huawei.com wrote: Hi Flavio, As test case name says, it is testing multiple bookie failures. On bookiefailure, when doing the ensemble reformation, unfortunately it is failing to connect to the Bookie-15039. But it should suppose to get connected and continue write operation. This is the reason for the test case failure. Please see the following log pattern: 2013-12-30 12:29:36,731 - INFO - [BookKeeperClientWorker-0-0:PerChannelBookieClient@167] - Connecting to bookie: /67.195.138.30:15039 2013-12-30 12:29:36,732 - ERROR - [New I/O client boss #5-1:PerChannelBookieClient$1@203] - Could not connect to bookie: [id: 0x019a639b, /229.27.250.246:46509 : /67.195.138.30:15039], current state CONNECTING 2013-12-30 12:29:36,732 - WARN - [BookKeeperClientWorker-0-0:PendingAddOp@158] - Write did not succeed: L0 E100 on /67.195.138.30:15039 2013-12-30 12:29:36,733 - INFO - [BookKeeperClientWorker-0-0:LedgerHandle@659] - Handling failure of bookie: /67.195.138.30:15039 index: 2 2013-12-30 12:29:36,733 - WARN - [BookKeeperClientWorker-0-0:RackawareEnsemblePlacementPolicy@491] - Failed to choose a bookie from /default-rack : excluded [Bookie: 67.195.138.30:15036, Bookie:67.195.138.30:15038, Bookie: 67.195.138.30:15039, Bookie:67.195.138.30:15040, Bookie: 67.195.138.30:15035], fallback to choose bookie randomly from the cluster. I'm thinking, there could be chance of small network fluctuations or slow machine and resulting in connection failure. To handle this IMHO, we should have netty client connection timeout in place and should retry for few intervals. Let me do a try with bootstrap.setOption(connectTimeoutMillis, timeoutvalue); Shall I raise a JIRA to discuss about these concerns and will reach to a conclusion. Whats your opinion? -Rakesh -Original Message- From: Flavio Junqueira [mailto:fpjunque...@yahoo.com] Sent: 31 December 2013 01:51 To: bookkeeper-dev@zookeeper.apache.org Subject: Fwd: Build failed in Jenkins: bookkeeper-trunk #489 I was wondering if there is a jira open for the test that failed below, does anyone know? -Flavio Begin forwarded message: Tests in error: testWithMultipleBookieFailuresInLastEnsemble[2](org.apache.bookkeeper.client.BookieWriteLedgerTest)
RE: Build failed in Jenkins: bookkeeper-trunk #489
Hi Sijie, But I didn't understand why the connection failure is immediately sending without waiting for the timeout. In general, client should wait for the connection timeout(10secs) and internally retries before throwing failure message. Am I correct? Do we need to have an explicit retry mechanism in netty? -Rakesh -Original Message- From: Sijie Guo [mailto:guosi...@gmail.com] Sent: 31 December 2013 11:59 To: bookkeeper-dev@zookeeper.apache.org Subject: Re: Build failed in Jenkins: bookkeeper-trunk #489 I don't think its connect timeout setting issue. as by default, netty channel connect timeout is 10 sec ( https://github.com/netty/netty/blob/3.2/src/main/java/org/jboss/netty/channel/DefaultChannelConfig.java#L38). If you checked the log, the log statements show that the connect operation is in same second. 2013-12-30 12:29:36,731 - INFO - [BookKeeperClientWorker-0-0:PerChannelBookieClient@167] - Connecting to bookie: /67.195.138.30:15039 2013-12-30 12:29:36,732 - ERROR - [New I/O client boss #5-1:PerChannelBookieClient$1@203] - Could not connect to bookie: [id: 0x019a639b, /229.27.250.246:46509 : /67.195.138.30:15039], current state CONNECTING On Mon, Dec 30, 2013 at 9:31 PM, Rakesh R rake...@huawei.com wrote: Hi Flavio, As test case name says, it is testing multiple bookie failures. On bookiefailure, when doing the ensemble reformation, unfortunately it is failing to connect to the Bookie-15039. But it should suppose to get connected and continue write operation. This is the reason for the test case failure. Please see the following log pattern: 2013-12-30 12:29:36,731 - INFO - [BookKeeperClientWorker-0-0:PerChannelBookieClient@167] - Connecting to bookie: /67.195.138.30:15039 2013-12-30 12:29:36,732 - ERROR - [New I/O client boss #5-1:PerChannelBookieClient$1@203] - Could not connect to bookie: [id: 0x019a639b, /229.27.250.246:46509 : /67.195.138.30:15039], current state CONNECTING 2013-12-30 12:29:36,732 - WARN - [BookKeeperClientWorker-0-0:PendingAddOp@158] - Write did not succeed: L0 E100 on /67.195.138.30:15039 2013-12-30 12:29:36,733 - INFO - [BookKeeperClientWorker-0-0:LedgerHandle@659] - Handling failure of bookie: /67.195.138.30:15039 index: 2 2013-12-30 12:29:36,733 - WARN - [BookKeeperClientWorker-0-0:RackawareEnsemblePlacementPolicy@491] - Failed to choose a bookie from /default-rack : excluded [Bookie: 67.195.138.30:15036, Bookie:67.195.138.30:15038, Bookie: 67.195.138.30:15039, Bookie:67.195.138.30:15040, Bookie: 67.195.138.30:15035], fallback to choose bookie randomly from the cluster. I'm thinking, there could be chance of small network fluctuations or slow machine and resulting in connection failure. To handle this IMHO, we should have netty client connection timeout in place and should retry for few intervals. Let me do a try with bootstrap.setOption(connectTimeoutMillis, timeoutvalue); Shall I raise a JIRA to discuss about these concerns and will reach to a conclusion. Whats your opinion? -Rakesh -Original Message- From: Flavio Junqueira [mailto:fpjunque...@yahoo.com] Sent: 31 December 2013 01:51 To: bookkeeper-dev@zookeeper.apache.org Subject: Fwd: Build failed in Jenkins: bookkeeper-trunk #489 I was wondering if there is a jira open for the test that failed below, does anyone know? -Flavio Begin forwarded message: Tests in error: testWithMultipleBookieFailuresInLastEnsemble[2](org.apache.bookkeeper. client.BookieWriteLedgerTest)
Re: Build failed in Jenkins: bookkeeper-trunk #489
On Mon, Dec 30, 2013 at 10:45 PM, Rakesh R rake...@huawei.com wrote: Hi Sijie, But I didn't understand why the connection failure is immediately sending without waiting for the timeout. In general, client should wait for the connection timeout(10secs) and internally retries before throwing failure message. Am I correct? No idea. from the log, there is less information to tell what was going on at that time. I think the better solution is to add logs about the failure so we could catch the details of what's wrong inside. Do we need to have an explicit retry mechanism in netty? I don't think we need retry connect in netty. As 1) we already have retry mechanism in bookie client ; 2) if connect failed on any bookie, we should let netty notify bookkeeper immediately. as connect failure means bookie down in most of case, we should change bookie immediately to avoid high latency. - Sijie -Rakesh -Original Message- From: Sijie Guo [mailto:guosi...@gmail.com] Sent: 31 December 2013 11:59 To: bookkeeper-dev@zookeeper.apache.org Subject: Re: Build failed in Jenkins: bookkeeper-trunk #489 I don't think its connect timeout setting issue. as by default, netty channel connect timeout is 10 sec ( https://github.com/netty/netty/blob/3.2/src/main/java/org/jboss/netty/channel/DefaultChannelConfig.java#L38 ). If you checked the log, the log statements show that the connect operation is in same second. 2013-12-30 12:29:36,731 - INFO - [BookKeeperClientWorker-0-0:PerChannelBookieClient@167] - Connecting to bookie: /67.195.138.30:15039 2013-12-30 12:29:36,732 - ERROR - [New I/O client boss #5-1:PerChannelBookieClient$1@203] - Could not connect to bookie: [id: 0x019a639b, /229.27.250.246:46509 : /67.195.138.30:15039], current state CONNECTING On Mon, Dec 30, 2013 at 9:31 PM, Rakesh R rake...@huawei.com wrote: Hi Flavio, As test case name says, it is testing multiple bookie failures. On bookiefailure, when doing the ensemble reformation, unfortunately it is failing to connect to the Bookie-15039. But it should suppose to get connected and continue write operation. This is the reason for the test case failure. Please see the following log pattern: 2013-12-30 12:29:36,731 - INFO - [BookKeeperClientWorker-0-0:PerChannelBookieClient@167] - Connecting to bookie: /67.195.138.30:15039 2013-12-30 12:29:36,732 - ERROR - [New I/O client boss #5-1:PerChannelBookieClient$1@203] - Could not connect to bookie: [id: 0x019a639b, /229.27.250.246:46509 : /67.195.138.30:15039], current state CONNECTING 2013-12-30 12:29:36,732 - WARN - [BookKeeperClientWorker-0-0:PendingAddOp@158] - Write did not succeed: L0 E100 on /67.195.138.30:15039 2013-12-30 12:29:36,733 - INFO - [BookKeeperClientWorker-0-0:LedgerHandle@659] - Handling failure of bookie: /67.195.138.30:15039 index: 2 2013-12-30 12:29:36,733 - WARN - [BookKeeperClientWorker-0-0:RackawareEnsemblePlacementPolicy@491] - Failed to choose a bookie from /default-rack : excluded [Bookie: 67.195.138.30:15036, Bookie:67.195.138.30:15038, Bookie: 67.195.138.30:15039, Bookie:67.195.138.30:15040, Bookie: 67.195.138.30:15035], fallback to choose bookie randomly from the cluster. I'm thinking, there could be chance of small network fluctuations or slow machine and resulting in connection failure. To handle this IMHO, we should have netty client connection timeout in place and should retry for few intervals. Let me do a try with bootstrap.setOption(connectTimeoutMillis, timeoutvalue); Shall I raise a JIRA to discuss about these concerns and will reach to a conclusion. Whats your opinion? -Rakesh -Original Message- From: Flavio Junqueira [mailto:fpjunque...@yahoo.com] Sent: 31 December 2013 01:51 To: bookkeeper-dev@zookeeper.apache.org Subject: Fwd: Build failed in Jenkins: bookkeeper-trunk #489 I was wondering if there is a jira open for the test that failed below, does anyone know? -Flavio Begin forwarded message: Tests in error: testWithMultipleBookieFailuresInLastEnsemble[2](org.apache.bookkeeper. client.BookieWriteLedgerTest)
[jira] [Created] (BOOKKEEPER-714) Logging channel exceptions in PerChannelBookieClient
Sijie Guo created BOOKKEEPER-714: Summary: Logging channel exceptions in PerChannelBookieClient Key: BOOKKEEPER-714 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-714 Project: Bookkeeper Issue Type: Bug Components: bookkeeper-client Reporter: Sijie Guo Assignee: Sijie Guo Fix For: 4.3.0 Logging channel exceptions in PerChannelBookieClient to identify channel connect issue. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
RE: Build failed in Jenkins: bookkeeper-trunk #489
I've tried one simple test case: Just before connecting 'bootstrap.connect(addr)', I have killed the Bookieserver. What I have observed is immediately returning the call with failure. Any thoughts? -Original Message- From: Sijie Guo [mailto:guosi...@gmail.com] Sent: 31 December 2013 12:33 To: bookkeeper-dev@zookeeper.apache.org Subject: Re: Build failed in Jenkins: bookkeeper-trunk #489 On Mon, Dec 30, 2013 at 10:45 PM, Rakesh R rake...@huawei.com wrote: Hi Sijie, But I didn't understand why the connection failure is immediately sending without waiting for the timeout. In general, client should wait for the connection timeout(10secs) and internally retries before throwing failure message. Am I correct? No idea. from the log, there is less information to tell what was going on at that time. I think the better solution is to add logs about the failure so we could catch the details of what's wrong inside. Do we need to have an explicit retry mechanism in netty? I don't think we need retry connect in netty. As 1) we already have retry mechanism in bookie client ; 2) if connect failed on any bookie, we should let netty notify bookkeeper immediately. as connect failure means bookie down in most of case, we should change bookie immediately to avoid high latency. - Sijie -Rakesh -Original Message- From: Sijie Guo [mailto:guosi...@gmail.com] Sent: 31 December 2013 11:59 To: bookkeeper-dev@zookeeper.apache.org Subject: Re: Build failed in Jenkins: bookkeeper-trunk #489 I don't think its connect timeout setting issue. as by default, netty channel connect timeout is 10 sec ( https://github.com/netty/netty/blob/3.2/src/main/java/org/jboss/netty/ channel/DefaultChannelConfig.java#L38 ). If you checked the log, the log statements show that the connect operation is in same second. 2013-12-30 12:29:36,731 - INFO - [BookKeeperClientWorker-0-0:PerChannelBookieClient@167] - Connecting to bookie: /67.195.138.30:15039 2013-12-30 12:29:36,732 - ERROR - [New I/O client boss #5-1:PerChannelBookieClient$1@203] - Could not connect to bookie: [id: 0x019a639b, /229.27.250.246:46509 : /67.195.138.30:15039], current state CONNECTING On Mon, Dec 30, 2013 at 9:31 PM, Rakesh R rake...@huawei.com wrote: Hi Flavio, As test case name says, it is testing multiple bookie failures. On bookiefailure, when doing the ensemble reformation, unfortunately it is failing to connect to the Bookie-15039. But it should suppose to get connected and continue write operation. This is the reason for the test case failure. Please see the following log pattern: 2013-12-30 12:29:36,731 - INFO - [BookKeeperClientWorker-0-0:PerChannelBookieClient@167] - Connecting to bookie: /67.195.138.30:15039 2013-12-30 12:29:36,732 - ERROR - [New I/O client boss #5-1:PerChannelBookieClient$1@203] - Could not connect to bookie: [id: 0x019a639b, /229.27.250.246:46509 : /67.195.138.30:15039], current state CONNECTING 2013-12-30 12:29:36,732 - WARN - [BookKeeperClientWorker-0-0:PendingAddOp@158] - Write did not succeed: L0 E100 on /67.195.138.30:15039 2013-12-30 12:29:36,733 - INFO - [BookKeeperClientWorker-0-0:LedgerHandle@659] - Handling failure of bookie: /67.195.138.30:15039 index: 2 2013-12-30 12:29:36,733 - WARN - [BookKeeperClientWorker-0-0:RackawareEnsemblePlacementPolicy@491] - Failed to choose a bookie from /default-rack : excluded [Bookie: 67.195.138.30:15036, Bookie:67.195.138.30:15038, Bookie: 67.195.138.30:15039, Bookie:67.195.138.30:15040, Bookie: 67.195.138.30:15035], fallback to choose bookie randomly from the cluster. I'm thinking, there could be chance of small network fluctuations or slow machine and resulting in connection failure. To handle this IMHO, we should have netty client connection timeout in place and should retry for few intervals. Let me do a try with bootstrap.setOption(connectTimeoutMillis, timeoutvalue); Shall I raise a JIRA to discuss about these concerns and will reach to a conclusion. Whats your opinion? -Rakesh -Original Message- From: Flavio Junqueira [mailto:fpjunque...@yahoo.com] Sent: 31 December 2013 01:51 To: bookkeeper-dev@zookeeper.apache.org Subject: Fwd: Build failed in Jenkins: bookkeeper-trunk #489 I was wondering if there is a jira open for the test that failed below, does anyone know? -Flavio Begin forwarded message: Tests in error: testWithMultipleBookieFailuresInLastEnsemble[2](org.apache.bookkeeper. client.BookieWriteLedgerTest)
Re: Build failed in Jenkins: bookkeeper-trunk #489
On Mon, Dec 30, 2013 at 11:16 PM, Rakesh R rake...@huawei.com wrote: I've tried one simple test case: Just before connecting 'bootstrap.connect(addr)', I have killed the Bookieserver. What I have observed is immediately returning the call with failure. Isn't that expected? as there is not server listened on given port. this is how TCP works, no? Any thoughts? -Original Message- From: Sijie Guo [mailto:guosi...@gmail.com] Sent: 31 December 2013 12:33 To: bookkeeper-dev@zookeeper.apache.org Subject: Re: Build failed in Jenkins: bookkeeper-trunk #489 On Mon, Dec 30, 2013 at 10:45 PM, Rakesh R rake...@huawei.com wrote: Hi Sijie, But I didn't understand why the connection failure is immediately sending without waiting for the timeout. In general, client should wait for the connection timeout(10secs) and internally retries before throwing failure message. Am I correct? No idea. from the log, there is less information to tell what was going on at that time. I think the better solution is to add logs about the failure so we could catch the details of what's wrong inside. Do we need to have an explicit retry mechanism in netty? I don't think we need retry connect in netty. As 1) we already have retry mechanism in bookie client ; 2) if connect failed on any bookie, we should let netty notify bookkeeper immediately. as connect failure means bookie down in most of case, we should change bookie immediately to avoid high latency. - Sijie -Rakesh -Original Message- From: Sijie Guo [mailto:guosi...@gmail.com] Sent: 31 December 2013 11:59 To: bookkeeper-dev@zookeeper.apache.org Subject: Re: Build failed in Jenkins: bookkeeper-trunk #489 I don't think its connect timeout setting issue. as by default, netty channel connect timeout is 10 sec ( https://github.com/netty/netty/blob/3.2/src/main/java/org/jboss/netty/ channel/DefaultChannelConfig.java#L38 ). If you checked the log, the log statements show that the connect operation is in same second. 2013-12-30 12:29:36,731 - INFO - [BookKeeperClientWorker-0-0:PerChannelBookieClient@167] - Connecting to bookie: /67.195.138.30:15039 2013-12-30 12:29:36,732 - ERROR - [New I/O client boss #5-1:PerChannelBookieClient$1@203] - Could not connect to bookie: [id: 0x019a639b, /229.27.250.246:46509 : /67.195.138.30:15039], current state CONNECTING On Mon, Dec 30, 2013 at 9:31 PM, Rakesh R rake...@huawei.com wrote: Hi Flavio, As test case name says, it is testing multiple bookie failures. On bookiefailure, when doing the ensemble reformation, unfortunately it is failing to connect to the Bookie-15039. But it should suppose to get connected and continue write operation. This is the reason for the test case failure. Please see the following log pattern: 2013-12-30 12:29:36,731 - INFO - [BookKeeperClientWorker-0-0:PerChannelBookieClient@167] - Connecting to bookie: /67.195.138.30:15039 2013-12-30 12:29:36,732 - ERROR - [New I/O client boss #5-1:PerChannelBookieClient$1@203] - Could not connect to bookie: [id: 0x019a639b, /229.27.250.246:46509 : /67.195.138.30:15039], current state CONNECTING 2013-12-30 12:29:36,732 - WARN - [BookKeeperClientWorker-0-0:PendingAddOp@158] - Write did not succeed: L0 E100 on /67.195.138.30:15039 2013-12-30 12:29:36,733 - INFO - [BookKeeperClientWorker-0-0:LedgerHandle@659] - Handling failure of bookie: /67.195.138.30:15039 index: 2 2013-12-30 12:29:36,733 - WARN - [BookKeeperClientWorker-0-0:RackawareEnsemblePlacementPolicy@491] - Failed to choose a bookie from /default-rack : excluded [Bookie: 67.195.138.30:15036, Bookie:67.195.138.30:15038, Bookie: 67.195.138.30:15039, Bookie:67.195.138.30:15040, Bookie: 67.195.138.30:15035], fallback to choose bookie randomly from the cluster. I'm thinking, there could be chance of small network fluctuations or slow machine and resulting in connection failure. To handle this IMHO, we should have netty client connection timeout in place and should retry for few intervals. Let me do a try with bootstrap.setOption(connectTimeoutMillis, timeoutvalue); Shall I raise a JIRA to discuss about these concerns and will reach to a conclusion. Whats your opinion? -Rakesh -Original Message- From: Flavio Junqueira [mailto:fpjunque...@yahoo.com] Sent: 31 December 2013 01:51 To: bookkeeper-dev@zookeeper.apache.org Subject: Fwd: Build failed in Jenkins: bookkeeper-trunk #489 I was wondering if there is a jira open for the test that failed below, does anyone know? -Flavio Begin forwarded message: Tests in error: testWithMultipleBookieFailuresInLastEnsemble[2](org.apache.bookkeeper. client.BookieWriteLedgerTest)
Re: Build failed in Jenkins: bookkeeper-trunk #489
On Mon, Dec 30, 2013 at 11:02 PM, Sijie Guo guosi...@gmail.com wrote: On Mon, Dec 30, 2013 at 10:45 PM, Rakesh R rake...@huawei.com wrote: Hi Sijie, But I didn't understand why the connection failure is immediately sending without waiting for the timeout. In general, client should wait for the connection timeout(10secs) and internally retries before throwing failure message. Am I correct? No idea. from the log, there is less information to tell what was going on at that time. I think the better solution is to add logs about the failure so we could catch the details of what's wrong inside. Created https://issues.apache.org/jira/browse/BOOKKEEPER-714 to add exception in logging, so we could catch more details when this test case failed. Do we need to have an explicit retry mechanism in netty? I don't think we need retry connect in netty. As 1) we already have retry mechanism in bookie client ; 2) if connect failed on any bookie, we should let netty notify bookkeeper immediately. as connect failure means bookie down in most of case, we should change bookie immediately to avoid high latency. - Sijie -Rakesh -Original Message- From: Sijie Guo [mailto:guosi...@gmail.com] Sent: 31 December 2013 11:59 To: bookkeeper-dev@zookeeper.apache.org Subject: Re: Build failed in Jenkins: bookkeeper-trunk #489 I don't think its connect timeout setting issue. as by default, netty channel connect timeout is 10 sec ( https://github.com/netty/netty/blob/3.2/src/main/java/org/jboss/netty/channel/DefaultChannelConfig.java#L38 ). If you checked the log, the log statements show that the connect operation is in same second. 2013-12-30 12:29:36,731 - INFO - [BookKeeperClientWorker-0-0:PerChannelBookieClient@167] - Connecting to bookie: /67.195.138.30:15039 2013-12-30 12:29:36,732 - ERROR - [New I/O client boss #5-1:PerChannelBookieClient$1@203] - Could not connect to bookie: [id: 0x019a639b, /229.27.250.246:46509 : /67.195.138.30:15039], current state CONNECTING On Mon, Dec 30, 2013 at 9:31 PM, Rakesh R rake...@huawei.com wrote: Hi Flavio, As test case name says, it is testing multiple bookie failures. On bookiefailure, when doing the ensemble reformation, unfortunately it is failing to connect to the Bookie-15039. But it should suppose to get connected and continue write operation. This is the reason for the test case failure. Please see the following log pattern: 2013-12-30 12:29:36,731 - INFO - [BookKeeperClientWorker-0-0:PerChannelBookieClient@167] - Connecting to bookie: /67.195.138.30:15039 2013-12-30 12:29:36,732 - ERROR - [New I/O client boss #5-1:PerChannelBookieClient$1@203] - Could not connect to bookie: [id: 0x019a639b, /229.27.250.246:46509 : /67.195.138.30:15039], current state CONNECTING 2013-12-30 12:29:36,732 - WARN - [BookKeeperClientWorker-0-0:PendingAddOp@158] - Write did not succeed: L0 E100 on /67.195.138.30:15039 2013-12-30 12:29:36,733 - INFO - [BookKeeperClientWorker-0-0:LedgerHandle@659] - Handling failure of bookie: /67.195.138.30:15039 index: 2 2013-12-30 12:29:36,733 - WARN - [BookKeeperClientWorker-0-0:RackawareEnsemblePlacementPolicy@491] - Failed to choose a bookie from /default-rack : excluded [Bookie: 67.195.138.30:15036, Bookie:67.195.138.30:15038, Bookie: 67.195.138.30:15039, Bookie:67.195.138.30:15040, Bookie: 67.195.138.30:15035], fallback to choose bookie randomly from the cluster. I'm thinking, there could be chance of small network fluctuations or slow machine and resulting in connection failure. To handle this IMHO, we should have netty client connection timeout in place and should retry for few intervals. Let me do a try with bootstrap.setOption(connectTimeoutMillis, timeoutvalue); Shall I raise a JIRA to discuss about these concerns and will reach to a conclusion. Whats your opinion? -Rakesh -Original Message- From: Flavio Junqueira [mailto:fpjunque...@yahoo.com] Sent: 31 December 2013 01:51 To: bookkeeper-dev@zookeeper.apache.org Subject: Fwd: Build failed in Jenkins: bookkeeper-trunk #489 I was wondering if there is a jira open for the test that failed below, does anyone know? -Flavio Begin forwarded message: Tests in error: testWithMultipleBookieFailuresInLastEnsemble[2](org.apache.bookkeeper. client.BookieWriteLedgerTest)
[jira] [Updated] (BOOKKEEPER-714) Logging channel exceptions in PerChannelBookieClient
[ https://issues.apache.org/jira/browse/BOOKKEEPER-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sijie Guo updated BOOKKEEPER-714: - Attachment: BOOKKEEPER-714.patch attach a patch to log channel exceptions, which could help investigating the test case failure. Logging channel exceptions in PerChannelBookieClient Key: BOOKKEEPER-714 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-714 Project: Bookkeeper Issue Type: Bug Components: bookkeeper-client Reporter: Sijie Guo Assignee: Sijie Guo Fix For: 4.3.0 Attachments: BOOKKEEPER-714.patch Logging channel exceptions in PerChannelBookieClient to identify channel connect issue. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
RE: Build failed in Jenkins: bookkeeper-trunk #489
oopz...you are right. -Original Message- From: Sijie Guo [mailto:guosi...@gmail.com] Sent: 31 December 2013 12:55 To: bookkeeper-dev@zookeeper.apache.org Subject: Re: Build failed in Jenkins: bookkeeper-trunk #489 On Mon, Dec 30, 2013 at 11:16 PM, Rakesh R rake...@huawei.com wrote: I've tried one simple test case: Just before connecting 'bootstrap.connect(addr)', I have killed the Bookieserver. What I have observed is immediately returning the call with failure. Isn't that expected? as there is not server listened on given port. this is how TCP works, no? Any thoughts? -Original Message- From: Sijie Guo [mailto:guosi...@gmail.com] Sent: 31 December 2013 12:33 To: bookkeeper-dev@zookeeper.apache.org Subject: Re: Build failed in Jenkins: bookkeeper-trunk #489 On Mon, Dec 30, 2013 at 10:45 PM, Rakesh R rake...@huawei.com wrote: Hi Sijie, But I didn't understand why the connection failure is immediately sending without waiting for the timeout. In general, client should wait for the connection timeout(10secs) and internally retries before throwing failure message. Am I correct? No idea. from the log, there is less information to tell what was going on at that time. I think the better solution is to add logs about the failure so we could catch the details of what's wrong inside. Do we need to have an explicit retry mechanism in netty? I don't think we need retry connect in netty. As 1) we already have retry mechanism in bookie client ; 2) if connect failed on any bookie, we should let netty notify bookkeeper immediately. as connect failure means bookie down in most of case, we should change bookie immediately to avoid high latency. - Sijie -Rakesh -Original Message- From: Sijie Guo [mailto:guosi...@gmail.com] Sent: 31 December 2013 11:59 To: bookkeeper-dev@zookeeper.apache.org Subject: Re: Build failed in Jenkins: bookkeeper-trunk #489 I don't think its connect timeout setting issue. as by default, netty channel connect timeout is 10 sec ( https://github.com/netty/netty/blob/3.2/src/main/java/org/jboss/nett y/ channel/DefaultChannelConfig.java#L38 ). If you checked the log, the log statements show that the connect operation is in same second. 2013-12-30 12:29:36,731 - INFO - [BookKeeperClientWorker-0-0:PerChannelBookieClient@167] - Connecting to bookie: /67.195.138.30:15039 2013-12-30 12:29:36,732 - ERROR - [New I/O client boss #5-1:PerChannelBookieClient$1@203] - Could not connect to bookie: [id: 0x019a639b, /229.27.250.246:46509 : /67.195.138.30:15039], current state CONNECTING On Mon, Dec 30, 2013 at 9:31 PM, Rakesh R rake...@huawei.com wrote: Hi Flavio, As test case name says, it is testing multiple bookie failures. On bookiefailure, when doing the ensemble reformation, unfortunately it is failing to connect to the Bookie-15039. But it should suppose to get connected and continue write operation. This is the reason for the test case failure. Please see the following log pattern: 2013-12-30 12:29:36,731 - INFO - [BookKeeperClientWorker-0-0:PerChannelBookieClient@167] - Connecting to bookie: /67.195.138.30:15039 2013-12-30 12:29:36,732 - ERROR - [New I/O client boss #5-1:PerChannelBookieClient$1@203] - Could not connect to bookie: [id: 0x019a639b, /229.27.250.246:46509 : /67.195.138.30:15039], current state CONNECTING 2013-12-30 12:29:36,732 - WARN - [BookKeeperClientWorker-0-0:PendingAddOp@158] - Write did not succeed: L0 E100 on /67.195.138.30:15039 2013-12-30 12:29:36,733 - INFO - [BookKeeperClientWorker-0-0:LedgerHandle@659] - Handling failure of bookie: /67.195.138.30:15039 index: 2 2013-12-30 12:29:36,733 - WARN - [BookKeeperClientWorker-0-0:RackawareEnsemblePlacementPolicy@491] - Failed to choose a bookie from /default-rack : excluded [Bookie: 67.195.138.30:15036, Bookie:67.195.138.30:15038, Bookie: 67.195.138.30:15039, Bookie:67.195.138.30:15040, Bookie: 67.195.138.30:15035], fallback to choose bookie randomly from the cluster. I'm thinking, there could be chance of small network fluctuations or slow machine and resulting in connection failure. To handle this IMHO, we should have netty client connection timeout in place and should retry for few intervals. Let me do a try with bootstrap.setOption(connectTimeoutMillis, timeoutvalue); Shall I raise a JIRA to discuss about these concerns and will reach to a conclusion. Whats your opinion? -Rakesh -Original Message- From: Flavio Junqueira [mailto:fpjunque...@yahoo.com] Sent: 31 December 2013 01:51 To: bookkeeper-dev@zookeeper.apache.org Subject: Fwd: Build failed in Jenkins: bookkeeper-trunk #489 I was wondering if there is a jira open for the test that failed below, does anyone know? -Flavio Begin
[jira] [Created] (BOOKKEEPER-715) bookie: delay dropping journal cached pages
Sijie Guo created BOOKKEEPER-715: Summary: bookie: delay dropping journal cached pages Key: BOOKKEEPER-715 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-715 Project: Bookkeeper Issue Type: Sub-task Components: bookkeeper-server Reporter: Sijie Guo Assignee: Sijie Guo Fix For: 4.3.0 As journal writes aren't aligned to sector size, if bookie drops cached pages immediately, journal has to read those pages again, which would impact journal write performance. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
