[
https://issues.apache.org/jira/browse/BOOKKEEPER-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924462#comment-15924462
]
ASF GitHub Bot commented on BOOKKEEPER-1008:
--------------------------------------------
Github user revans2 commented on the issue:
https://github.com/apache/bookkeeper/pull/116
Also it looks like Jenkins failed with some findbugs issues. The logs say
that it timed out but when I run it I get
```
INFO] --- findbugs-maven-plugin:3.0.3:check (default-cli) @
bookkeeper-server ---
[INFO] BugInstance size is 4
[INFO] Error size is 0
[INFO] Total bugs: 4
[INFO] Dead store to ledgerId in
org.apache.bookkeeper.bookie.FileInfo.setExplicitLac(ByteBuffer)
[org.apache.bookkeeper.bookie.FileInfo] At FileInfo.java:[line 140]
DLS_DEAD_LOCAL_STORE
[INFO] Inconsistent synchronization of
org.apache.bookkeeper.bookie.FileInfo.explicitLac; locked 85% of time
[org.apache.bookkeeper.bookie.FileInfo, org.apache.bookkeeper.bookie.FileInfo,
org.apache.bookkeeper.bookie.FileInfo, org.apache.bookkeeper.bookie.FileInfo,
org.apache.bookkeeper.bookie.FileInfo, org.apache.bookkeeper.bookie.FileInfo,
org.apache.bookkeeper.bookie.FileInfo, org.apache.bookkeeper.bookie.FileInfo,
org.apache.bookkeeper.bookie.FileInfo, org.apache.bookkeeper.bookie.FileInfo,
org.apache.bookkeeper.bookie.FileInfo, org.apache.bookkeeper.bookie.FileInfo,
org.apache.bookkeeper.bookie.FileInfo, org.apache.bookkeeper.bookie.FileInfo]
Unsynchronized access at FileInfo.java:[line 118]Unsynchronized access at
FileInfo.java:[line 145]Synchronized access at FileInfo.java:[line
121]Synchronized access at FileInfo.java:[line 122]Synchronized access at
FileInfo.java:[line 123]Synchronized access at FileInfo.java:[line
124]Synchronized access at FileInfo.java:[line 125]Synchronized access at
FileInfo.java:[line 134]Synchronized access at FileInfo.java:[line
137]Synchronized access at FileInfo.java:[line 138]Synchronized access at
FileInfo.java:[line 140]Synchronized access at FileInfo.java:[line
135]Synchronized access at FileInfo.java:[line 141]Synchronized access at
FileInfo.java:[line 143] IS2_INCONSISTENT_SYNC
[INFO] Inconsistent synchronization of
org.apache.bookkeeper.client.LedgerHandle.length; locked 90% of time
[org.apache.bookkeeper.client.ReadOnlyLedgerHandle$MetadataUpdater,
org.apache.bookkeeper.client.LedgerHandle,
org.apache.bookkeeper.client.LedgerHandle,
org.apache.bookkeeper.client.LedgerHandle,
org.apache.bookkeeper.client.LedgerHandle,
org.apache.bookkeeper.client.LedgerHandle,
org.apache.bookkeeper.client.LedgerHandle,
org.apache.bookkeeper.client.LedgerHandle,
org.apache.bookkeeper.client.LedgerHandle,
org.apache.bookkeeper.client.LedgerRecoveryOp,
org.apache.bookkeeper.client.LedgerHandle$2] Unsynchronized access at
ReadOnlyLedgerHandle.java:[line 59]Synchronized access at
LedgerHandle.java:[line 259]Synchronized access at LedgerHandle.java:[line
778]Synchronized access at LedgerHandle.java:[line 778]Synchronized access at
LedgerHandle.java:[line 1362]Synchronized access at LedgerHandle.java:[line
249]Synchronized access at LedgerHandle.java:[line 249]Synchronized access at
LedgerHandle.java:[line 250]Synchronized access at LedgerHandle.java:[line
977]Synchronized access at LedgerRecoveryOp.java:[line 151]Synchronized access
at LedgerHandle.java:[line 379] IS2_INCONSISTENT_SYNC
[INFO] Futile attempt to change max pool size of
ScheduledThreadPoolExecutor in new
org.apache.bookkeeper.util.OrderedSafeExecutor(String, int, ThreadFactory,
StatsLogger, boolean, long) [org.apache.bookkeeper.util.OrderedSafeExecutor] At
OrderedSafeExecutor.java:[line 186]
DMI_FUTILE_ATTEMPT_TO_CHANGE_MAXPOOL_SIZE_OF_SCHEDULED_THREAD_POOL_EXECUTOR
[INFO]
```
All of these look like they are unrelated to the patch though
> Move to netty4
> --------------
>
> Key: BOOKKEEPER-1008
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1008
> Project: Bookkeeper
> Issue Type: Improvement
> Components: bookkeeper-client, bookkeeper-server
> Affects Versions: 4.5.0
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
>
> As part of the Yahoo push back and in general we would like to move to netty
> 4, preferably netty 4.1.x for the client and server communication.
> This lays the ground work for zero copy, or very nearly zero copy handling on
> the server side.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
