[
https://issues.apache.org/jira/browse/BOOKKEEPER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416019#comment-13416019
]
Rakesh R commented on BOOKKEEPER-199:
-------------------------------------
Thanks all for your time and inputs. Based on the discussion which we had in
this jira, identified the following subtasks to implement the r-o mode
incrementally.
# Utility functions for checking disk problem
# Detect IOExceptions on entrylogger and bookie should consider next ledger
dir(if any)
# Detect IOExceptions on ledger cache and bookie should consider next ledger
dir(if any)
# Provide mechanism to detect r-o bookie by the bookie clients
# Provide admin command to start the bookie in read-only mode (Raised as a
suggestion)
-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
> Fix For: 4.2.0
>
> 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
