[
https://issues.apache.org/jira/browse/BOOKKEEPER-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485569#comment-13485569
]
Rakesh R commented on BOOKKEEPER-347:
-------------------------------------
Adding more to my above ??comment#1??:
We could also think of an optimistic approach of sending the write request to
bkserver(without extra r-o checks), anyway bookie server has the logic of
validating r-o mode and throws BookieProtocol.EREADONLY exception back to the
client. So in the client side, just handle "BookieProtocol.EREADONLY" and finds
new bookie server to continue writing entries.
> 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
