You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2014/05/30 15:26:02 UTC

[jira] [Updated] (BOOKKEEPER-673) Ledger length can be inaccurate in failure case

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

Ivan Kelly updated BOOKKEEPER-673:
----------------------------------

    Fix Version/s: 4.2.3

> Ledger length can be inaccurate in failure case
> -----------------------------------------------
>
>                 Key: BOOKKEEPER-673
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-673
>             Project: Bookkeeper
>          Issue Type: Bug
>            Reporter: Ivan Kelly
>            Assignee: Sijie Guo
>             Fix For: 4.3.0, 4.2.3
>
>         Attachments: BOOKKEEPER-673.patch
>
>
> Ledger length can be inconsistent if a ledger is closed by a writing client that encounters an error. For example, in a cluster with 3 bookies, and an ledger with a q3e3 configuration, if a bookie dies, the client will close the ledger when it fails to write an entry. However, it has already added the length of the failed entry to the local ledger length, and this is what is stored to zk.



--
This message was sent by Atlassian JIRA
(v6.2#6252)