[
https://issues.apache.org/jira/browse/BOOKKEEPER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438453#comment-13438453
]
Vinay commented on BOOKKEEPER-199:
----------------------------------
Following are the benifits we will get than the approach given in BOOKKEEPER-345
1) Less changes in the main code flow
2) No synchronization required between addEntry(..) and flush(..) as used in
BOOKKEEPER-345, hence not affecting any performance.
3) No need to maintain any duplicate entries anywhere.
4) Since we are detecting the disk over usage well ahead of reaching 100% disk
usage, we will not loose any written data.
Anyway, this new thread will not be doing any heavy operation(Only check the
disk usages periodically).
So adding this thread will not impact the performace of the system.
> 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
