[
https://issues.apache.org/jira/browse/CASSANDRA-6646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13935399#comment-13935399
]
sankalp kohli commented on CASSANDRA-6646:
------------------------------------------
The patch looks straightforward. The only thing is that now with default
setting of stop for disk failure policy, Cassandra will stop on any bad stable.
Also work done in CASSANDRA-2261 will not matter here as Cassandra will stop on
any bad stable.
I would vote for the behavior in this ticket as you should replace your drive
on corruption.
> Disk Failure Policy ignores CorruptBlockException
> --------------------------------------------------
>
> Key: CASSANDRA-6646
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6646
> Project: Cassandra
> Issue Type: Bug
> Reporter: sankalp kohli
> Assignee: Marcus Eriksson
> Priority: Minor
> Fix For: 2.0.7, 2.1 beta2
>
> Attachments:
> 0001-make-CorruptSSTableException-an-FSError-to-be-able-t.patch
>
>
> If Cassandra is using compression and has a bad drive or stable, it will
> throw an CorruptBlockException.
> Disk Failure Policy only works if it is an FSError and does not work for
> IOExceptions like this.
> We need to better handle such exceptions as it causes nodes to not respond to
> the co-ordinator causing the client to timeout.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
