[
https://issues.apache.org/jira/browse/BOOKKEEPER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13265654#comment-13265654
]
Uma Maheswara Rao G commented on BOOKKEEPER-199:
------------------------------------------------
{quote}
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.
{quote}
When flush fails (assuming disk failed here), why do we need to turn it to read
only automatically?
I think admin should get the failure notice, instead of silently turning out to
read only mode.
See the cases in Namenode and Datanode, we will shutdown the nodes when all
disks failed in the node. So, that admin can take the actions to replace with
the good node or correcting the existing one. I did not get the actual use case
of read only mode. When we have only one disk and if it fails we may have to
shutdown the node right?
If we have other cases for it, it would be great if we have this feature as
optional. Could you please clarify more on requirement perspective? is it like
safemode? how this node can recover in-future?
> 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
