[
https://issues.apache.org/jira/browse/BOOKKEEPER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242308#comment-13242308
]
Rakesh R commented on BOOKKEEPER-199:
-------------------------------------
Following are just some thoughts to take the first step:
# *ledger flushing throws IOException:*
Say bookie has multiple ledger dirs -> /tmp/bk1-data, /tmp/bk2-data)
On IOException, bookie should consider next ledger dir and probably mark the
tried dirs as BAD_FOR_WRITE, so this will not be selected next time. Finally,
if there is no success, then switch bookie to r-o mode.
# *Journal flushing throws IOException:*
Immediately switch to r-o mode. AFAIK, there is no multiple dirs for the
journal.
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
>
> 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
