[
https://issues.apache.org/jira/browse/BOOKKEEPER-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764079#comment-13764079
]
Hadoop QA commented on BOOKKEEPER-673:
--------------------------------------
Testing JIRA BOOKKEEPER-673
Patch
[BOOKKEEPER-673.patch|https://issues.apache.org/jira/secure/attachment/12602517/BOOKKEEPER-673.patch]
downloaded at Wed Sep 11 07:15:10 UTC 2013
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:green}+1{color} the patch does not introduce any line longer than
120
. {color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 FINDBUGS{color}
. {color:green}+1{color} the patch does not seem to introduce new Findbugs
warnings
{color:green}+1 TESTS{color}
. Tests run: 880
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/bookkeeper-trunk-precommit-build/491/
> 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 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
