[
https://issues.apache.org/jira/browse/BOOKKEEPER-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293358#comment-13293358
]
Rakesh R commented on BOOKKEEPER-199:
-------------------------------------
Here One more scenario needs to be handled which was discussed on
BOOKKEEPER-180.
Adding new ledger and flushing is failed in SyncThread due to disk full. But
Server did not shutdown here.
2012-06-11 140014,696 - ERROR [SyncThreadInterleavedLedgerStorage@156] -
Exception flushing Ledger
{noformat}
java.io.IOException No space left on device
at sun.nio.ch.FileDispatcher.write0(Native Method)
at sun.nio.ch.FileDispatcher.write(FileDispatcher.java39)
at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java69)
at sun.nio.ch.IOUtil.write(IOUtil.java26)
at sun.nio.ch.FileChannelImpl.write(FileChannelImpl.java198)
at
org.apache.bookkeeper.bookie.BufferedChannel.flush(BufferedChannel.java109)
at org.apache.bookkeeper.bookie.EntryLogger.flush(EntryLogger.java280)
at
org.apache.bookkeeper.bookie.InterleavedLedgerStorage.flush(InterleavedLedgerStorage.java154)
at org.apache.bookkeeper.bookie.Bookie$SyncThread.run(Bookie.java200)
{noformat}
> 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
