[
https://issues.apache.org/jira/browse/BOOKKEEPER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13249822#comment-13249822
]
Rakesh R commented on BOOKKEEPER-199:
-------------------------------------
Hi Sijie/Ivan,
I have attached the initial patch.
Here I have tried to make the server r-o mode only on ledger failures(untouched
existing logic of, bookie shutdown on journal failures) and simultaneously will
update r-o status on its corresponding ephemeral entry on ZK. This status will
be lost on server restart. Otw I could use persistent node, but there is a
chance of orphan entries, if I restart the server with diff ip/port. Please
give opinion on this or any thoughts.
I will also try to add more test cases.
Thanks,
Rakesh
> Provide bookie readonly mode, when journal/ledgers flushing has failed with
> IOE
> -------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-199
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-199
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-server
> Affects Versions: 4.0.0
> Reporter: Rakesh R
> Assignee: Rakesh R
> Priority: Critical
> Attachments: BOOKKEEPER-199.patch
>
>
> Bookkeeper should change to readonly(r-o) mode when the journal/ledgers
> flushing has failed with IOException. Later on, reject write requests on
> server side and will accept only the read requests from the clients, because
> even if flushing fails, the data in the bookie which has been flushed is
> still valid.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
