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

Posted to dev@bookkeeper.apache.org by "Vinay (JIRA)" <ji...@apache.org> on 2013/06/12 06:46:20 UTC

[jira] [Created] (BOOKKEEPER-623) Metadata is having extra Segment which is causing AutoRecovery to fail

Vinay created BOOKKEEPER-623:
--------------------------------

             Summary: Metadata is having extra Segment which is causing AutoRecovery to fail
                 Key: BOOKKEEPER-623
                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-623
             Project: Bookkeeper
          Issue Type: Bug
          Components: bookkeeper-server
    Affects Versions: 4.2.1
            Reporter: Vinay
            Assignee: Vinay


With the almost same testcase mentioned in the BOOKKEEPER-584, Ledger metadata is getting added with extra segment during failure handling of bookies along with fencing. 

Only difference in the testcase is .
1. Before bookie failures some entries were already written
2. And after bookies failed ( First bookie will throw LedgerFenced/Unauthorized exception, and second bookie is slow/dead bookie ), Number of entries written asynchrounously is n*ensembleSize+1

Note that, Unauthorized/FencedException callback comes first, then other bookie failure callback comes.

I will attach a TestCase along with patch for this shortly. Testcase is modified version of attached testcase in BOOKKEEPER-584


--
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