[
https://issues.apache.org/jira/browse/BOOKKEEPER-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Kelly updated BOOKKEEPER-632:
----------------------------------
Attachment: 0001-BOOKKEEPER-632-AutoRecovery-should-consider-read-onl.patch
Fixed the problem. The ZK expire test was in the wrong place after the change.
> AutoRecovery should consider read only bookies
> ----------------------------------------------
>
> Key: BOOKKEEPER-632
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-632
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-auto-recovery, bookkeeper-server
> Affects Versions: 4.2.1, 4.3.0
> Reporter: Vinay
> Assignee: Vinay
> Fix For: 4.2.2, 4.3.0
>
> Attachments:
> 0001-BOOKKEEPER-632-AutoRecovery-should-consider-read-onl.patch,
> 0001-BOOKKEEPER-632-AutoRecovery-should-consider-read-onl.patch,
> 0001-BOOKKEEPER-632-AutoRecovery-should-consider-read-onl.patch,
> BOOKKEEPER-632-branch-4.2.patch, BOOKKEEPER-632-branch-4.2.patch,
> BOOKKEEPER-632.patch, BOOKKEEPER-632.patch, BOOKKEEPER-632.patch,
> BOOKKEEPER-632.patch, BOOKKEEPER-632.patch, BOOKKEEPER-632.patch,
> BOOKKEEPER-632.patch, BOOKKEEPER-632.patch
>
>
> Autorecovery Auditor should consider the readonly bookies as Available
> Bookies while publishing the under-replicated ledgers.
> Also AutoRecoveryDaemon should shutdown if the local bookie is readonly
--
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
