[
https://issues.apache.org/jira/browse/BOOKKEEPER-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878329#comment-13878329
]
Sijie Guo commented on BOOKKEEPER-643:
--------------------------------------
{quote}
What I mean is that they never get closed through normal operation. The only
place I see them being closed is in #shutdown and #removeFromChannelsAndClose
(called from removeEntryLog). So, the channels are only closed when the log is
either deleted or the bookie shuts down.
{quote}
It is not the issue introduced by this jira. This jira js just to improve
concurrency, which doesn't change too much behavior. I could open a ticket to
use Guava cache to maintain opened entry log files.
> Improve concurrency of entry logger
> -----------------------------------
>
> Key: BOOKKEEPER-643
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-643
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-server
> Affects Versions: 4.2.0
> Reporter: Aniruddha
> Assignee: Aniruddha
> Fix For: 4.3.0
>
> Attachments: BOOKKEEPER-643.diff, BOOKKEEPER-643.diff,
> BOOKKEEPER-643.diff
>
>
> the jira is created as part of BOOKKEEPER-429 to improve concurrency of
> current bookie implementation by leverage concurrent structures.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
