[
https://issues.apache.org/jira/browse/CASSANDRA-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420057#comment-13420057
]
Aleksey Yeschenko commented on CASSANDRA-2116:
----------------------------------------------
{quote}
The status quo is "IOE or RTE." IOE is superseded by FSWE, and RTE can stay the
same. If we need to improve things beyond that, it's out of scope for this
ticket.
{quote}
Just to be clear: by IOE here I meant IOException, not IOError. I was thinking
about KeysIndex#forceBlockingFlush that is (was) wrapping ExecutionException
AND InterruptedException in IOException just because the interface allowed only
IOEx.
But I agree with you regarding "drop the "throws IOException" declaration from
applyIndexUpdates". At one point I actually did just that. Will do.
> Separate out filesystem errors from generic IOErrors
> ----------------------------------------------------
>
> Key: CASSANDRA-2116
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2116
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Chris Goffinet
> Assignee: Aleksey Yeschenko
> Fix For: 1.2
>
> Attachments:
> 0001-Issue-2116-Replace-some-IOErrors-with-more-informati.patch,
> 0001-Separate-out-filesystem-errors-from-generic-IOErrors.patch,
> CASSANDRA-2116-v3.patch
>
>
> We throw IOErrors everywhere today in the codebase. We should separate out
> specific errors such as (reading, writing) from filesystem into FSReadError
> and FSWriteError. This makes it possible in the next ticket to allow certain
> failure modes (kill the server if reads or writes fail to disk).
--
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
