[
https://issues.apache.org/jira/browse/BOOKKEEPER-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400390#comment-13400390
]
Ivan Kelly commented on BOOKKEEPER-278:
---------------------------------------
The disable mechanism is to avoid false rereplication processes from happening
when a bookie is taken down for upgrade. Valid rereplication tasks still need
to run, which is fine. We can let them continue. They may fail due to the
bookie being rereplicated being taken down for upgrade, but it's ok because the
admin should run a health check on the cluster after upgrading all bookies
anyhow.
> Ability to disable auto recovery temporarily
> --------------------------------------------
>
> Key: BOOKKEEPER-278
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-278
> Project: Bookkeeper
> Issue Type: Sub-task
> Reporter: Ivan Kelly
> Assignee: Rakesh R
> Fix For: 4.2.0
>
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
