[
https://issues.apache.org/jira/browse/BOOKKEEPER-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Kelly resolved BOOKKEEPER-764.
-----------------------------------
Resolution: Fixed
Fix Version/s: (was: 4.2.3)
(was: 4.3.0)
Actually, I had read it wrong. prevLength is never really used anyhow.
> Possible inconsistency in length when closing the ledger due to pending adds
> being closed after prevLength recorded
> -------------------------------------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-764
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-764
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Ivan Kelly
> Assignee: Ivan Kelly
>
> As the summary says, we drain the pending adds after recording prevLength,
> which means that prevLength will be too long and may be written to the
> metadata if there is a version conflict.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
