You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "John Sumsion (JIRA)" <ji...@apache.org> on 2014/09/13 21:49:33 UTC

[jira] [Commented] (CASSANDRA-7927) Kill daemon on any disk error

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

John Sumsion commented on CASSANDRA-7927:
-----------------------------------------

NOTE: patch is based on CASSANDRA-7507, and adds tests for that patch also

> Kill daemon on any disk error
> -----------------------------
>
>                 Key: CASSANDRA-7927
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7927
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>         Environment: aws, stock cassandra or dse
>            Reporter: John Sumsion
>              Labels: lhf
>             Fix For: 2.1.1
>
>         Attachments: 7927-v1-die.patch
>
>
> We got a disk read error on 1.2.13 that didn't trigger the disk failure policy, and I'm trying to hunt down why, but in doing so, I saw that there is no disk_failure_policy option for just killing the daemon.
> If we ever get a corrupt sstable, we want to replace the node anyway, because some aws instance store disks just go bad.
> I want to use the JVMStabilityInspector from CASSANDRA-7507 to kill so that remains standard, so I will base my patch on CASSANDRA-7507.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)