[
https://issues.apache.org/jira/browse/BOOKKEEPER-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458537#comment-13458537
]
Uma Maheswara Rao G commented on BOOKKEEPER-278:
------------------------------------------------
Hi Ivan,
>From above Rakesh comments, I think it is doing what you are expecting right?
{quote}
# When Auditor recieved any failure notification, it will get lost
bookie/ledgers and during "markLedgerUnderreplicated" seeing "disable" znode
then add a znode watcher and enters to WAITING state.
{quote}
from the above order,
{quote}
1.The disable Znode is set.
2.A is taken down for upgrade.
{quote}
first it added the disable Znode, so, markLedgerUnderreplicated call from
Auditor will check for disable Znode existence as per Rakesh comments.
So, it seems to me that, you both are in the same lines here right?
I have not looked at patch yet, So, you pointed something wrong in the patch
which are leading for this comments?
@Rakesh, Ivan, Please correct me, if I understood wrongly about your comments.
> 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
