[
https://issues.apache.org/jira/browse/BOOKKEEPER-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989541#comment-15989541
]
Kishore Kasi Udayashankar commented on BOOKKEEPER-1008:
-------------------------------------------------------
[~eolivelli] I have pushed my local changes to git repo. Sure, I will not
squash any new changes I make. Looks like another instance of refcount issue in
the code. Let me take a look again. Yahoo's bookkeeper changes are in
"yahoo-4.3" branch.
Netty supported linux EPOLL transport in 4.x version, which provides better
performance over NIO transport. My changes to upgrade to Netty 4.1 leverages
EPOLL to take advantage of the performance again that comes with it. The past
few days I have been investigating a problem I noticed in using EPOLL transport.
Few Bookeeper tests pause/resume a subset of bookies by using Netty constructs
to stop/resume request processing. With EPOLL transport I notice that pause on
the bookies does not immediately stop accepting bookie client requests. I have
approached Netty community to figure out if there is a way to get around this
issue. I don't have a solution yet. [~revans2] Not sure if yahoo has seen this
issue with EPOLL transport. IMHO we should use NIO and enable EPOLL once I have
a solution to this issue.
> 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)
