[
https://issues.apache.org/jira/browse/BOOKKEEPER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416374#comment-13416374
]
Uma Maheswara Rao G commented on BOOKKEEPER-199:
------------------------------------------------
{quote}
got it. I think we don't need to separate it in a task. otherwise, I don't know
which method is used and which method is not used. you could add it in
BOOKKEEPER-345. and BOOKKEEPER-346 is based on BOOKKEEPER-345. how about doing
in this way?
{quote}
+1
@Rakesh,
{quote}
Yes true. r-o is a subset of available bookies, make sense keeping under
available znode and will have the exclusion logic.
{quote}
make sense to me. On other thought, how about creating something like
'available-readonly' node, so that we can avoid excluding logics
> 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: Bug
> 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
