[
https://issues.apache.org/jira/browse/BOOKKEEPER-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719248#comment-13719248
]
Sijie Guo commented on BOOKKEEPER-604:
--------------------------------------
this change is still buggy. still leaking on following code block.
{code}
if (firstEntryList.size() == 0) {
LOG.debug("Nothing to flush for ledger {}.", l);
// nothing to do
return;
}
{code}
> Ledger storage can log an exception if GC happens concurrently.
> ---------------------------------------------------------------
>
> Key: BOOKKEEPER-604
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-604
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Ivan Kelly
> Assignee: Ivan Kelly
> Fix For: 4.2.2, 4.3.0
>
> Attachments:
> 0001-BOOKKEEPER-604-Ledger-storage-can-log-an-exception-i.patch,
> 0001-BOOKKEEPER-604-Ledger-storage-can-log-an-exception-i.patch,
> 0001-BOOKKEEPER-604-Ledger-storage-can-log-an-exception-i.patch,
> 0001-BOOKKEEPER-604-Ledger-storage-can-log-an-exception-i.patch,
> BOOKKEEPER-604.diff
>
>
> If a ledger is flushing, and part way through,GC kicks in, it can delete the
> index file before we try and flush it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
