[
https://issues.apache.org/jira/browse/BOOKKEEPER-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543975#comment-13543975
]
Hadoop QA commented on BOOKKEEPER-355:
--------------------------------------
Testing JIRA BOOKKEEPER-355
Patch
[0001-BOOKKEEPER-355-Ledger-recovery-will-mark-ledger-as-c.patch|https://issues.apache.org/jira/secure/attachment/12563287/0001-BOOKKEEPER-355-Ledger-recovery-will-mark-ledger-as-c.patch]
downloaded at Fri Jan 4 14:42:14 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 2 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:red}-1 TESTS{color} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/bookkeeper-trunk-precommit-build/197/
> Ledger recovery will mark ledger as closed with -1, in case of slow bookie is
> added to ensemble during recovery add
> --------------------------------------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-355
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-355
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-server
> Affects Versions: 4.1.0, 4.2.0
> Reporter: Vinay
> Assignee: Ivan Kelly
> Fix For: 4.2.0
>
> Attachments:
> 0001-BOOKKEEPER-355-Ledger-recovery-will-mark-ledger-as-c.patch,
> 0001-BOOKKEEPER-355-Ledger-recovery-will-mark-ledger-as-c.patch,
> 0001-BOOKKEEPER-355-Ledger-recovery-will-mark-ledger-as-c.patch,
> 0001-BOOKKEEPER-355-Ledger-recovery-will-mark-ledger-as-c.patch,
> 0001-BOOKKEEPER-355-Ledger-recovery-will-mark-ledger-as-c.patch,
> 0003-BOOKKEEPER-355-Ledger-recovery-will-mark-ledger-as-c.patch,
> BOOKKEEPER-355.patch, BOOKKEEPER-355.patch
>
>
> Scenario:
> ------------
> 1. Ledger is created with ensemble and quorum size as 2, written with one
> entry
> 2. Now first bookie is in the ensemble is made down.
> 3. Another client fence and trying to recover the same ledger
> 4. During this time ensemble change will happen and new bookie will be added.
> But this bookie is not able to connect.
> 5. This recovery will fail.
> 7. Now previously added bookie came up.
> 8. Another client trying to recover the same ledger.
> 9. Since new bookie is first in the ensemble, doRecoveryRead() is reading
> from that bookie and getting NoSuchLedgerException and closing the ledger
> with -1
> i.e. Marking the ledger as empty, even though first client had successfully
> written one entry.
--
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
