[
https://issues.apache.org/jira/browse/BOOKKEEPER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423029#comment-13423029
]
Hudson commented on BOOKKEEPER-349:
-----------------------------------
Integrated in bookkeeper-trunk #620 (See
[https://builds.apache.org/job/bookkeeper-trunk/620/])
BOOKKEEPER-349: Entry logger should close all the chennels which are there
in Map, instead of closing only current channel. (umamaheswararao via sijie)
(Revision 1365869)
Result = UNSTABLE
sijie :
Files :
* /zookeeper/bookkeeper/trunk/CHANGES.txt
*
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/EntryLogger.java
> Entry logger should close all the chennels which are there in Map, instead of
> closing only current channel.
> -----------------------------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-349
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-349
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-server
> Affects Versions: 4.1.0
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-349.patch
>
>
> I have seen this on restarting the same bookies from same JVM( in one of mey
> testcase which I was writing for autoRecovery work), i.e, all channels are
> not getting closed.
> When we restart the same bookie, there are 0.log channel will be a older
> channel. Since the current code cares about only current logChannel. So, we
> are not releasing the older channels on EntryLogger shutdown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
