[
https://issues.apache.org/jira/browse/BOOKKEEPER-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794286#comment-13794286
]
Hudson commented on BOOKKEEPER-673:
-----------------------------------
SUCCESS: Integrated in bookkeeper-trunk #401 (See
[https://builds.apache.org/job/bookkeeper-trunk/401/])
BOOKKEEPER-673: Ledger length can be inaccurate in failure case (sijie via
ivank) (ivank: rev 1531970)
* /zookeeper/bookkeeper/trunk/CHANGES.txt
*
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/LedgerHandle.java
*
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/PendingAddOp.java
*
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/test/java/org/apache/bookkeeper/client/LedgerCloseTest.java
> 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
>
> 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.1#6144)
