[
https://issues.apache.org/jira/browse/BOOKKEEPER-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431766#comment-13431766
]
Vinay commented on BOOKKEEPER-345:
----------------------------------
Thanks [~hustlmsp] for taking a look here.
{quote}why need it? I remembered FileChannel would throw IOException if disk is
full. please correct me if I am wrong{quote}
I also thought same way, but during testing I encountered a problem where,
FileChannel was not throwing exception sometimes on disk full and all contents
was not flushed properly.
And during reading that entry log was corrupted, and was not able to read
entres. After adding this check, same problem did not occur.
Regarding other comments, I will try to fix and post a patch soon on review
board.
> Detect IOExceptions on entrylogger and bookie should consider next ledger
> dir(if any)
> -------------------------------------------------------------------------------------
>
> Key: BOOKKEEPER-345
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-345
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-server
> Affects Versions: 4.1.0
> Reporter: Rakesh R
> Attachments: BOOKKEEPER-345.patch
>
>
> This jira to detect IOExceptions in "EntryLogger", and will iterate over all
> the configured ledger(s) on IOException. Finally if no writable dirs
> available, will move bookie to r-o mode(if this mode is enabled).
> By default(r-o mode will be disabled) the bookie will shutdown if no writable
> disk available.
--
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
