[
https://issues.apache.org/jira/browse/BOOKKEEPER-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450732#comment-13450732
]
Ivan Kelly commented on BOOKKEEPER-278:
---------------------------------------
This patch won't actually disable the rereplication, it'll just delay it. Using
this the admin would disbale the replication workers, but the auditor would
continue to see bookie's dropping off, and marking all the ledgers as
underreplicated. Then once reenabled, the replication workered would go about
rereplicating everything. They probably wouldn't actually rereplicate much,
because the check at the start wouldn't show much many missing segments, but
still, it's not a side effect we want. It would be better to disable at the
auditor level.
On a side note, checking the ledgers after a rolling upgrade is a good idea,
but I get the impression it wasn't intentional here.
> Ability to disable auto recovery temporarily
> --------------------------------------------
>
> Key: BOOKKEEPER-278
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-278
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-auto-recovery
> Affects Versions: 4.0.0
> Reporter: Ivan Kelly
> Assignee: Rakesh R
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-278.patch
>
>
> Administrators will need to do rolling upgrades of bookies. If auto recovery
> is enabled during a rolling upgrade, there will be a lot of thrashing of
> ledgers as they recovery gets kicked off. Therefore we need a way to
> temporarily disable it.
--
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
