[CASSANDRA-7927] Kill daemon on any disk error

• Type: New Feature
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.1.2
• Labels: bootcamp lhf

Environment

aws, stock cassandra or dse

• Assignee: John Sumsion
• Reporter: John Sumsion

Authors

John Sumsion

Reviewers

Joshua McKenzie

• Created: 13/Sep/14 17:11
• Updated: 16/Apr/19 09:31
• Resolved: 24/Oct/14 17:39

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.

Issue Links

• depends upon: CASSANDRA-7507 OOM creates unreliable state - die instantly better
• is depended upon by: CASSANDRA-7579 File descriptor exhaustion can lead to unreliable state in exception condition
• relates to: CASSANDRA-9635 Silent startup failure with filesystem that does not support mmap