[
https://issues.apache.org/jira/browse/BOOKKEEPER-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994841#comment-15994841
]
ASF GitHub Bot commented on BOOKKEEPER-1008:
--------------------------------------------
Github user revans2 commented on the issue:
https://github.com/apache/bookkeeper/pull/116
@eolivelli I get them too. It may be differences in the default value of
ulimit. Probably the simplest thing to do it to try and trace down who is
leaking all of the file descriptors. It most likely is a missed close and
falling back to GC to issue the close.
> 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)
