[
https://issues.apache.org/jira/browse/CASSANDRA-6646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13938647#comment-13938647
]
sankalp kohli edited comment on CASSANDRA-6646 at 3/18/14 1:16 AM:
-------------------------------------------------------------------
The patch looks quite straight forward. This will work for us.
We might also want to add another option to stop cassandra after we see error
in x different stables.
was (Author: kohlisankalp):
The patch looks quite straight forward. This will work for us.
We might also want to add another option to stop cassandra after x stable
failures.
> 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-add-paranoid-disk-failure-option.patch,
> 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)
