[
https://issues.apache.org/jira/browse/BOOKKEEPER-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Merli reopened BOOKKEEPER-596:
-------------------------------------
It seems like the issue is not completely fixed by this patch, it looks
probably worse.
I've verified that after a garbage collection cleaning, some ledgers (whose
metadata is untouched in ZK) were delete from the bookies. This eventually
triggers error when either adding entries to these ledgers (infinite loop in
the client.. ) or when reading (entries not found).
This was using the HiearchicalLedgerManager (not sure the issue applies to all
ledgers managers).
I'm trying to isolate a simple way to reproduce the issue, for now I think it's
more likely to happen when a big number of ledgers are deleted in a short time
and hence collected in the same gc cycle.
> Ledgers are gc'ed by mistake in MSLedgerManagerFactory.
> -------------------------------------------------------
>
> Key: BOOKKEEPER-596
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-596
> Project: Bookkeeper
> Issue Type: Bug
> Affects Versions: 4.2.0, 4.2.1
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Priority: Blocker
> Fix For: 4.2.2, 4.3.0
>
> Attachments:
> 0001-BOOKKEEPER-596-Ledgers-are-gc-ed-by-mistake-in-MSLed.patch,
> 0001-BOOKKEEPER-596-Ledgers-are-gc-ed-by-mistake-in-MSLed.patch,
> BOOKKEEPER-596.patch, BOOKKEEPER-596.patch, BOOKKEEPER-596.patch
>
>
> details:
> https://issues.apache.org/jira/browse/BOOKKEEPER-590?focusedCommentId=13616397&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13616397
--
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
