[jira] [Resolved] (BOOKKEEPER-348) Last entry will be lost when open an un-closed ledger

["Ivan Kelly (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Kelly resolved BOOKKEEPER-348.
-----------------------------------
    Resolution: Not A Bug

> Last entry will be lost when open an un-closed ledger 
> ------------------------------------------------------
>
>                 Key: BOOKKEEPER-348
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-348
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: bookkeeper-client
>    Affects Versions: 4.1.0
>            Reporter: Wangda Tan (No longer used)
>         Attachments: BookKeeper-348.patch
>
>
> This can be reproduced in following steps:
> 1) client-A created a ledger-x and write N entries to it
> 2) client-B open the ledger-x and try to read all entries from it. client-B can only get N-1 entries (except for the last entry)
> This problem caused by, when trying to open an unclosed ledger, it will enter the "recover" mode, it can get correct last entry-Id judged by the size of log file. But it will set the new opened ledger's lastAddConfirmed by the previous lastAddConfirmed, and the entry-id will be ignored.
> For an unclosed ledger, the lastAddConfirmed will always = (last-entry-id - 1).
> A patch attached to this jira.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)