[
https://issues.apache.org/jira/browse/BOOKKEEPER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268086#comment-13268086
]
Uma Maheswara Rao G commented on BOOKKEEPER-199:
------------------------------------------------
Thanks a lot, Flavio and Sijie for your opinions.
@Falvio
{quote}
One option I see is to have the bookie removing itself from the list of
available bookies in zookeeper so that the administrator is able to determine
that the bookie has declared itself faulty. The administrator can be notified
of the change through a zookeeper watcher. In the meanwhile, the bookie is able
to respond to read requests for which it has data. How does it sound?
{quote}
Agreed.
{quote}
So how about make it as a strategy, user could decide shutting down or turning
to read-only when encountering a faulty bookie?
{quote}
Sounds good to me.
Just adding config parameter for this option also should be ok. if we enable
it, Bookie will turn automatically to read-only mode. If we don't enable it, it
will sutdown by default. Admins also can start the bookie in read-only mode
explicitly.
> 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
