Build failed in Jenkins: bookkeeper-master #1281

2016-02-09 Thread Apache Jenkins Server 
See 

Changes:

[sijie] BOOKKEEPER-883: Test timeout in bookkeeper-benchmark

[sijie] BOOKKEEPER-890: Concurrent modification exception when removing listener

[sijie] BOOKKEEPER-892: Bookie sanity test

[sijie] BOOKKEEPER-888: Dispatch individual callbacks from journal in different

[sijie] BOOKKEEPER-886: Allow to disable ledgers operation throttling

[sijie] BOOKKEEPER-893: explicitly call bk shutdown to set the exit code

[sijie] BOOKKEEPER-891: Read entries failure should trigger callback only once

--
[...truncated 532 lines...]
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) @ 
hedwig-server-compat420 ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.0:testCompile (default-testCompile) @ 
hedwig-server-compat420 ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.9:test (default-test) @ 
hedwig-server-compat420 ---
[INFO] Surefire report directory: 


---
 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-server-compat420 
---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-shade-plugin:1.5:shade (default) @ hedwig-server-compat420 ---
[INFO] Including org.apache.bookkeeper:hedwig-server:jar:4.2.0 in the shaded 
jar.
[INFO] Excluding org.slf4j:slf4j-api:jar:1.6.4 from the shaded jar.
[INFO] Excluding org.slf4j:slf4j-log4j12:jar:1.6.4 from the shaded jar.
[INFO] Including org.apache.bookkeeper:hedwig-client:jar:4.2.0 in the shaded 
jar.
[INFO] Including org.apache.bookkeeper:hedwig-protocol:jar:4.2.0 in the shaded 
jar.
[INFO] Including org.jboss.netty:netty:jar:3.2.4.Final in the shaded jar.
[INFO] Including commons-configuration:commons-configuration:jar:1.6 in the 
shaded jar.
[INFO] Including commons-collections:commons-collections:jar:3.2.1 in the 
shaded jar.
[INFO] Including commons-lang:commons-lang:jar:2.4 in the shaded jar.
[INFO] Including commons-logging:commons-logging:jar:1.1.1 in the shaded jar.
[INFO] Including commons-digester:commons-digester:jar:1.8 in the shaded jar.
[INFO] Excluding commons-beanutils:commons-beanutils:jar:1.7.0 from the shaded 
jar.
[INFO] Excluding commons-beanutils:commons-beanutils-core:jar:1.8.0 from the 
shaded jar.
[INFO] Including org.apache.derby:derby:jar:10.8.2.2 in the shaded jar.
[INFO] Including org.apache.zookeeper:zookeeper:jar:3.4.3 in the shaded jar.
[INFO] Including org.apache.bookkeeper:bookkeeper-server:jar:4.2.0 in the 
shaded jar.
[INFO] Excluding com.google.protobuf:protobuf-java:jar:2.4.1 from the shaded 
jar.
[INFO] Excluding com.google.guava:guava:jar:13.0.1 from the shaded jar.
[INFO] Including commons-cli:commons-cli:jar:1.2 in the shaded jar.
[INFO] Including commons-codec:commons-codec:jar:1.6 in the shaded jar.
[INFO] Including commons-io:commons-io:jar:2.1 in the shaded jar.
[INFO] Excluding log4j:log4j:jar:1.2.15 from the shaded jar.
[INFO] Excluding jline:jline:jar:0.9.94 from the shaded jar.
[INFO] Excluding junit:junit:jar:3.8.1 from the shaded jar.
[INFO] Replacing original artifact with shaded artifact.
[INFO] Replacing 

 with 

[INFO] 
[INFO] >>> findbugs-maven-plugin:2.5.2:check (default-cli) @ 
hedwig-server-compat420 >>>
[INFO] 
[INFO] --- findbugs-maven-plugin:2.5.2:findbugs (findbugs) @ 
hedwig-server-compat420 ---
[INFO] 
[INFO] <<< findbugs-maven-plugin:2.5.2:check (default-cli) @ 
hedwig-server-compat420 <<<
[INFO] 
[INFO] --- findbugs-maven-plugin:2.5.2:check (default-cli) @ 
hedwig-server-compat420 ---
[INFO] 
[INFO] 
[INFO] Building hedwig-protocol 4.4.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ hedwig-protocol -

[jira] [Commented] (BOOKKEEPER-892) Add a sanity test to help identify bookie nodes with problems that prevent writes but is still registered in ZK

2016-02-09 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138891#comment-15138891
 ] 

Hudson commented on BOOKKEEPER-892:
---

FAILURE: Integrated in bookkeeper-master #1281 (See 
[https://builds.apache.org/job/bookkeeper-master/1281/])
BOOKKEEPER-892: Bookie sanity test (sijie: rev 
61390322ea591bcfe3186e289c27f331c86941ad)
* bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/BookieShell.java
* 
bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/LocalBookieEnsemblePlacementPolicy.java


> Add a sanity test to help identify bookie nodes with problems that prevent 
> writes but is still registered in ZK
> ---
>
> Key: BOOKKEEPER-892
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-892
> Project: Bookkeeper
>  Issue Type: Test
>  Components: bookkeeper-server
>Affects Versions: 4.3.2
>Reporter: Siddharth Sunil Boobna
>Assignee: Siddharth Sunil Boobna
>Priority: Minor
> Fix For: 4.4.0
>
>
> Bookie Shell should have a sanity test to identify any problems with the 
> local bookie that is still registered in ZK.
> Solution:
> Add a sanity test to the bookie shell that will create a ledger locally, 
> write/read few entries and delete the ledger. To test only the local bookie, 
> the ledger ensemble size will be 1 and we implement a 
> LocalBookieEnsemblePlacementPolicy.



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

[jira] [Commented] (BOOKKEEPER-893) bookie exited with status 0 on journal I/O exception

2016-02-09 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138896#comment-15138896
 ] 

Hudson commented on BOOKKEEPER-893:
---

FAILURE: Integrated in bookkeeper-master #1281 (See 
[https://builds.apache.org/job/bookkeeper-master/1281/])
BOOKKEEPER-893: explicitly call bk shutdown to set the exit code (sijie: rev 
63395a3e3d9bb253ea2745042631e44a3d195ea0)
* bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/BookieServer.java


> bookie exited with status 0 on journal I/O exception
> 
>
> Key: BOOKKEEPER-893
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-893
> Project: Bookkeeper
>  Issue Type: Bug
>  Components: bookkeeper-server
>Affects Versions: 4.3.2
>Reporter: Siddharth Sunil Boobna
>Assignee: Siddharth Sunil Boobna
>Priority: Minor
> Fix For: 4.4.0
>
>
> {noformat}
> 06:13:32.041 [BookieJournal-3181] ERROR org.apache.bookkeeper.bookie.Journal 
> - I/O exception in Journal thread!
> java.nio.channels.ClosedChannelException: null
> at sun.nio.ch.FileChannelImpl.ensureOpen(FileChannelImpl.java:110) 
> ~[na:1.8.0_60]
> at sun.nio.ch.FileChannelImpl.position(FileChannelImpl.java:253) 
> ~[na:1.8.0_60]
> at org.apache.bookkeeper.bookie.Journal.run(Journal.java:964) 
> ~[bookkeeper-server-4.3.1.33.jar:4.3.1]
> 06:13:32.041 [BookieJournal-3181] INFO  org.apache.bookkeeper.bookie.Journal 
> - Journal exited loop!
> 06:13:32.041 [Bookie-3181] ERROR org.apache.bookkeeper.bookie.Bookie  - 
> Journal manager quits unexpectedly.
> 06:13:32.042 [Bookie-3181] INFO  org.apache.bookkeeper.bookie.Bookie  - 
> Triggering shutdown of Bookie-3181 with exitCode 5
> 06:13:32.042 [BookieShutdownTrigger] INFO  
> org.apache.bookkeeper.bookie.Bookie  - Shutting down Bookie-3181 with 
> exitCode 5
> 06:13:32.044 [main] INFO  o.a.bookkeeper.proto.BookieServer- Stop stats 
> provider
> 06:13:32.045 [bookie-reg-0] INFO  org.apache.zookeeper.ZooKeeper   - 
> Session: 0x14ff63dc02cbd02 closed
> 06:13:32.045 [bookie-reg-0-EventThread] INFO  org.apache.zookeeper.ClientCnxn 
>  - EventThread shut down
> 06:13:32.045 [BookieShutdownTrigger] INFO  
> org.apache.bookkeeper.bookie.Journal - Shutting down Journal
> 06:13:32.046 [Thread-2] INFO  o.a.bookkeeper.proto.BookieServer- Shutting 
> down BookieServer
> 06:13:32.046 [Thread-2] INFO  o.a.b.proto.BookieNettyServer- Shutting 
> down BookieNettyServer
> 06:13:32.046 [ForceWriteThread] ERROR org.apache.bookkeeper.bookie.Journal - 
> ForceWrite thread interrupted
> java.lang.InterruptedException: null
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2014)
>  ~[na:1.8.0_60]
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2048)
>  ~[na:1.8.0_60]
> at 
> org.apache.bookkeeper.util.UnboundArrayBlockingQueue.take(UnboundArrayBlockingQueue.java:312)
>  ~[bookkeeper-server-4.3.1.33.jar:4.3.1]
> at 
> org.apache.bookkeeper.bookie.Journal$ForceWriteThread.run(Journal.java:448) 
> ~[bookkeeper-server-4.3.1.33.jar:4.3.1]
> ...
> 06:13:32.184 [bookie-io-0] WARN  i.n.channel.DefaultChannelPipeline   - An 
> exceptionCaught() event was fired, and it reached at the tail of the 
> pipeline. It usually means the last handler in the pipeline did not handle 
> the exception.
> java.nio.channels.ClosedChannelException: null
> {noformat}
> When the bookie shuts down due to some exception, it exits with exitCode 0. 
> We try to get the exitCode when calling System.exit() here:
> https://github.com/apache/bookkeeper/blob/master/bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/BookieServer.java#L400
> But the exitCode is set by the shutdown hook which is triggered by 
> System.exit(). Thus, we will always exit with code 0.
> Solution:
> We explicitly call bookie shutdown to set the exit code.



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

[jira] [Commented] (BOOKKEEPER-891) Read entries failure should trigger callback only once

2016-02-09 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138892#comment-15138892
 ] 

Hudson commented on BOOKKEEPER-891:
---

FAILURE: Integrated in bookkeeper-master #1281 (See 
[https://builds.apache.org/job/bookkeeper-master/1281/])
BOOKKEEPER-891: Read entries failure should trigger callback only once (sijie: 
rev 9c937f5d814d4079b6134db361a0e2de1e37cd05)
* 
bookkeeper-server/src/main/java/org/apache/bookkeeper/client/PendingReadOp.java
* 
bookkeeper-server/src/test/java/org/apache/bookkeeper/client/BookKeeperTest.java


> Read entries failure should trigger callback only once
> --
>
> Key: BOOKKEEPER-891
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-891
> Project: Bookkeeper
>  Issue Type: Bug
>Reporter: Matteo Merli
>Assignee: Matteo Merli
>Priority: Minor
> Fix For: 4.4.0
>
>
> When reading multiple entries with 
> {code}LedgerHandle.asyncReadEntries(){code}, in case there is a read error, 
> the callback is currently being invoked for each of the requested entries. 
> Since a single "success" callback is expected, we should also have a single 
> "failure" callback invocation.



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

[jira] [Commented] (BOOKKEEPER-886) Allow to disable ledgers operation throttling

2016-02-09 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138893#comment-15138893
 ] 

Hudson commented on BOOKKEEPER-886:
---

FAILURE: Integrated in bookkeeper-master #1281 (See 
[https://builds.apache.org/job/bookkeeper-master/1281/])
BOOKKEEPER-886: Allow to disable ledgers operation throttling (sijie: rev 
d96a2db912278e3d88ed59d8d3e15b62bc37ffd4)
* 
bookkeeper-server/src/main/java/org/apache/bookkeeper/client/PendingReadOp.java
* 
bookkeeper-server/src/main/java/org/apache/bookkeeper/conf/ClientConfiguration.java
* bookkeeper-server/src/main/java/org/apache/bookkeeper/client/LedgerHandle.java


> Allow to disable ledgers operation throttling
> -
>
> Key: BOOKKEEPER-886
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-886
> Project: Bookkeeper
>  Issue Type: Improvement
>Reporter: Matteo Merli
>Assignee: Matteo Merli
>Priority: Minor
> Fix For: 4.4.0
>
>
> In the bookie client there is a throttling mechanism that is rate-limiting 
> the number of writes/s done on a particular ledger. The default value is 5000 
> entries/s written on a ledger.
> Trying to write faster will block the calling thread, which may not be 
> desirable in an asynchronous server.
> We should be able to disable the throttling, if the application wants to 
> control the rate with different mechanisms.



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

[jira] [Commented] (BOOKKEEPER-883) Test timeout in bookkeeper-benchmark

2016-02-09 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138895#comment-15138895
 ] 

Hudson commented on BOOKKEEPER-883:
---

FAILURE: Integrated in bookkeeper-master #1281 (See 
[https://builds.apache.org/job/bookkeeper-master/1281/])
BOOKKEEPER-883: Test timeout in bookkeeper-benchmark (sijie: rev 
8729d12be50295086e7440dfa5d0256abb7688d5)
* 
bookkeeper-server/src/main/java/org/apache/bookkeeper/meta/FlatLedgerManager.java
* 
bookkeeper-server/src/main/java/org/apache/bookkeeper/meta/ZkLedgerIdGenerator.java
* 
bookkeeper-benchmark/src/test/java/org/apache/bookkeeper/benchmark/TestBenchmark.java
* 
bookkeeper-benchmark/src/main/java/org/apache/bookkeeper/benchmark/BenchReadThroughputLatency.java


> Test timeout in bookkeeper-benchmark
> 
>
> Key: BOOKKEEPER-883
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-883
> Project: Bookkeeper
>  Issue Type: Bug
>Reporter: Sijie Guo
>Assignee: Sijie Guo
> Fix For: 4.4.0, 4.3.2
>
>
> bookkeeper-benchmark tests usually timeout



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

[jira] [Commented] (BOOKKEEPER-890) Concurrent modification exception when removing listener in Bookkeeper ZK ledger manager

2016-02-09 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138890#comment-15138890
 ] 

Hudson commented on BOOKKEEPER-890:
---

FAILURE: Integrated in bookkeeper-master #1281 (See 
[https://builds.apache.org/job/bookkeeper-master/1281/])
BOOKKEEPER-890: Concurrent modification exception when removing listener 
(sijie: rev 626b7e8bb0b84271df97cfbf0a1b157c6cfe5a18)
* 
bookkeeper-server/src/main/java/org/apache/bookkeeper/meta/AbstractZkLedgerManager.java


> Concurrent modification exception when removing listener in Bookkeeper ZK 
> ledger manager
> 
>
> Key: BOOKKEEPER-890
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-890
> Project: Bookkeeper
>  Issue Type: Bug
>Affects Versions: 4.3.2
>Reporter: Matteo Merli
>Assignee: Matteo Merli
>Priority: Minor
> Fix For: 4.4.0
>
>
> The listener set is modified while iterating through it.
> {noformat}
> 00:20:00.283 [main-EventThread] INFO  o.a.b.meta.AbstractZkLedgerManager   - 
> Unregistered ledger metadata listener ReadOnlyLedgerHandle(lid = 10454, id = 
> 839729832) on ledger 10454.
> 00:20:00.283 [main-EventThread] ERROR org.apache.zookeeper.ClientCnxn  - 
> Error while calling watcher 
> java.util.ConcurrentModificationException: null
> at java.util.HashMap$HashIterator.nextNode(HashMap.java:1429) 
> ~[na:1.8.0_60]
> at java.util.HashMap$KeyIterator.next(HashMap.java:1453) 
> ~[na:1.8.0_60]
> at 
> org.apache.bookkeeper.meta.AbstractZkLedgerManager.process(AbstractZkLedgerManager.java:207)
>  ~[bookkeeper-server-4.3.1.36.jar:4.3.1]
> at 
> org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:522) 
> [zookeeper-3.4.6.jar:3.4.6-1569965]
> at 
> org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498) 
> [zookeeper-3.4.6.jar:3.4.6-1569965]
> {noformat}



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

[jira] [Commented] (BOOKKEEPER-888) Dispatch individual callbacks from journal in different threads

2016-02-09 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138894#comment-15138894
 ] 

Hudson commented on BOOKKEEPER-888:
---

FAILURE: Integrated in bookkeeper-master #1281 (See 
[https://builds.apache.org/job/bookkeeper-master/1281/])
BOOKKEEPER-888: Dispatch individual callbacks from journal in different (sijie: 
rev 63a2a91eba191e92a1902cf5400325dcf4d36089)
* bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/Journal.java


> Dispatch individual callbacks from journal in different threads
> ---
>
> Key: BOOKKEEPER-888
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-888
> Project: Bookkeeper
>  Issue Type: Improvement
>Reporter: Matteo Merli
>Assignee: Matteo Merli
>Priority: Minor
> Fix For: 4.4.0
>
>
> Currently the journal is sending all the responses from a single thread, 
> after the entries in a batch are synced. Since a thread pool has been 
> configured, it is better to spread the send-response tasks to all the 
> available threads.



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

[jira] [Created] (BOOKKEEPER-894) Read ledger entries from the bookie shell

2016-02-09 Thread Siddharth Sunil Boobna (JIRA) 
Siddharth Sunil Boobna created BOOKKEEPER-894:
-

 Summary: Read ledger entries from the bookie shell
 Key: BOOKKEEPER-894
 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-894
 Project: Bookkeeper
  Issue Type: Improvement
  Components: bookkeeper-server
Affects Versions: 4.3.2
Reporter: Siddharth Sunil Boobna
Assignee: Siddharth Sunil Boobna
Priority: Minor


Bookie Shell should have a tool to read ledger entries from the bookkeeper 
cluster with optional arguments of startEntryId and endEntryId.

Solution:
We implement readEntries() in BookKeeperAdmin and return an Iterable. While 
iterating through it, we fetch individual entries instead of fetching all 
entries at once. Also, if the lastEntryId is not specified, we read entries 
till we get a NoSuchEntryException



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