cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-7927) Kill daemon on any disk error
Date Sat, 13 Sep 2014 19:38:33 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-7927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Joshua McKenzie updated CASSANDRA-7927:
---------------------------------------
    Description: 
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.

  was:
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 JVMIntrospector from CASSANDRA-7507 to kill so that remains standard, so
I will base my patch on CASSANDRA-7507.


> 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
>             Fix For: 2.1.1
>
>
> 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)

Mime
View raw message