[
https://issues.apache.org/jira/browse/BOOKKEEPER-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404894#comment-13404894
]
Uma Maheswara Rao G commented on BOOKKEEPER-247:
------------------------------------------------
Hi Ivan, Is it possible for you to mark the last fragment in ledger from
LedgerChecker?
So, that i can use this information in ReplicationWorker for fencing the
current writer.
This is the point what we have discussed in mailing list recently.
Also we have seen that case rarely 2 or 3 times in our testing till now.
So, I will try to fence if last fragment is underReplicated fragment.
Still I am thinking about introduce some delay(say 30sec, can be configarable)
for this kind of ledgers and if still ledger is in that situation then I will
fence.
Here hope is that, within that delay period, client may write the entries and
may reform the ensemble with good bookies, then that fragment would not be last
fragment in ensemble.
> 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
