[
https://issues.apache.org/jira/browse/BOOKKEEPER-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485832#comment-13485832
]
Vinay commented on BOOKKEEPER-347:
----------------------------------
Hi Rakesh,
"readonly" is the persistent znode, which is under "/ledgers/available" and if
any r-o bookies will be having ephemeral nodes under
"/ledgers/available/readonly".
As Sijie mentioned in
https://issues.apache.org/jira/browse/BOOKKEEPER-199?focusedCommentId=13416144&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13416144
only write requests will go through available bookies and we need exclude r-o
bookies from available bookies list. Here since "readonly" znode also under
"/ledgers/available", Just excluding it.
Since BookieWatcher itself will exclude from available list, no need of extra
checking of whether bookie is readonly or not at client side.
Requests, which have sent before BookieWatcher updates the available list,
will get "BookieProtocol.EREADONLY" error. And again ensemble change will
happen excluding the r-o bookies.
> Provide mechanism to detect r-o bookie by the bookie clients
> -------------------------------------------------------------
>
> Key: BOOKKEEPER-347
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-347
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-client
> Affects Versions: 4.1.0
> Reporter: Rakesh R
> Assignee: Vinay
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-347.patch
>
>
> This jira to discuss, how the bookie client knows about the bookie running in
> r-o. This would be required by the client to choose writable bookies during
> add entries.
--
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
