[
https://issues.apache.org/jira/browse/BOOKKEEPER-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680942#comment-13680942
]
Vinay commented on BOOKKEEPER-623:
----------------------------------
Corrupted metadata will look like this
{noformat}BookieMetadataFormatVersion 2
quorumSize: 3
ensembleSize: 3
length: 56
lastEntryId: 9
state: CLOSED
segment {
ensembleMember: "xx.xx.xx.154:15002"
ensembleMember: "xx.xx.xx.154:15004"
ensembleMember: "xx.xx.xx.154:15001"
firstEntryId: 0
}
segment {
ensembleMember: "xx.xx.xx.154:15002"
ensembleMember: "xx.xx.xx.154:15005"
ensembleMember: "xx.xx.xx.154:15001"
firstEntryId: 10
}
digestType: CRC32
password: ""
ackQuorumSize: 3{noformat}
here ledger closed with lastEntryId 9, but still one more segment is present
with firstEntryId 10. And during autorecovery, bookie will try to read this
entry and fails.
> 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
