[
https://issues.apache.org/jira/browse/BOOKKEEPER-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13872266#comment-13872266
]
Rakesh R commented on BOOKKEEPER-661:
-------------------------------------
bq.On any unrelated note, why do we register readonly bookies in zookeeper. I
don't see it used anywhere on the client? Rakesh R, perhaps you remember?
Hi Ivan,
As I recollect, readonly bookie information is used in the following cases:
# Rereplication : Auditor will be using all the bookies(available + r-o
bookies) to see failures.
# There is a logic to close channels to dead bookies. This readonly bookieId is
used to make it alive and excluding from deadbookie list.
# Also, exposed shell command to know the r-o bookies
> Turn readonly back to writable if spaces are reclaimed.
> -------------------------------------------------------
>
> Key: BOOKKEEPER-661
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-661
> Project: Bookkeeper
> Issue Type: Improvement
> Components: bookkeeper-server
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Fix For: 4.3.0
>
> Attachments: BOOKKEEPER-661.diff, BOOKKEEPER-661.diff,
> BOOKKEEPER-661_662.diff
>
>
> should be able to turn a bookie from readonly back to writable if the spaces
> are reclaimed.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
