cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6646) Disk Failure Policy ignores CorruptBlockException
Date Mon, 17 Mar 2014 18:09:45 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13938131#comment-13938131
] 

Marcus Eriksson commented on CASSANDRA-6646:
--------------------------------------------

bq. rename to stop_paranoid
sure

it was introduced in CASSANDRA-6364 which was a 2.0-only fix, ill add it when i commit this

> 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)

Mime
View raw message