[
https://issues.apache.org/jira/browse/BOOKKEEPER-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13406950#comment-13406950
]
Uma Maheswara Rao G commented on BOOKKEEPER-247:
------------------------------------------------
Even though we treat this empty ledger as underReplicated due to the above
lastAddConfirmed++, we will post pone this ledger as last fragment is
underReplicated and it is in open state. After pendingReplication timeout, this
ledger will get force fenced.
That means, after adding the PendingReplicationWorker logic and
ReplicationWorker logic, there won't be any ledger in open state more than
PendingReplication grace period interval. Ofcource this is configurable. Is
this behaviour fine with you all?
> 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
