[
https://issues.apache.org/jira/browse/BOOKKEEPER-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13406918#comment-13406918
]
Uma Maheswara Rao G commented on BOOKKEEPER-247:
------------------------------------------------
Current writer only can get the lastConfirmed entry correctly.
Here LedgerChecker will not be a Writer in any case, considering one entry
extra will the option to go i feel.
{code}
long lastAddConfirmed = lh
.getLastAddConfirmed();
if(lh.metadata.isClosed() == false){
lastAddConfirmed++;
}
fragments.add(new LedgerFragment(lh.getId(), curEntryId,
lastAddConfirmed, i, curEnsemble, lh
.getDistributionSchedule()));
{code}
with this, above given test passed. Infact all other tests also should modify
to use different LedgerHandle. otherwise this will make the test failures ,
because writer will anyway get lastConfirmed correctly.
> Detection of under replication
> ------------------------------
>
> Key: BOOKKEEPER-247
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-247
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-client, bookkeeper-server
> Reporter: Ivan Kelly
> Assignee: Ivan Kelly
> Attachments: BOOKKEEPER-247.diff, BOOKKEEPER-247.diff,
> BOOKKEEPER-247.patch, BOOKKEEPER-247.patch
>
>
> This JIRA discusses how the bookkeeper system will detect underreplication of
> ledger entries.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
