cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6646) Disk Failure Policy ignores CorruptBlockException
Date Mon, 17 Mar 2014 18:05:43 GMT


Jonathan Ellis commented on CASSANDRA-6646:

sorry to bikeshed myself, maybe rename to stop_paranoid to emphasize that it shares behavior
with stop?

where did stopTransports get introduced?  i don't see it on trunk.

> Disk Failure Policy ignores CorruptBlockException 
> --------------------------------------------------
>                 Key: CASSANDRA-6646
>                 URL:
>             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

View raw message