[
https://issues.apache.org/jira/browse/BOOKKEEPER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268067#comment-13268067
]
Sijie Guo commented on BOOKKEEPER-199:
--------------------------------------
shutting down a bookie or turning it to read-only depends on applications. For
HDFS NameNode, it might be critical to shut down a faulty bookie immediately,
For a pub/sub case, turning a bookie server into read-only case, it could make
a bookie still serving read-request which doesn't affect message traffic. So
how about make it as a strategy, user could decide shutting down or turning to
read-only when encountering a faulty bookie?
I agreed Flavio's option about failure noticeable. Beside that, another option
for JMX monitoring is that we could expose bookie status thru JMX, if a bookie
is turned to read-only, admin could be alerted by JMX value changing.
> 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
