[
https://issues.apache.org/jira/browse/BOOKKEEPER-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989799#comment-15989799
]
Enrico Olivelli commented on BOOKKEEPER-1008:
---------------------------------------------
Jusr dropping the classifier from the epool dependency will make the source
code compilable and at run time the libs will not be available for tests and we
will fall back to nio. This way in tests we will not get into the pause issues
of netty.
I think that the pause is not used for a real bookie in production so this is
not a blocker issue for us.
Does this idea sound good to you?
> 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)
