Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-7927

Kill daemon on any disk error

    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Fix Version/s: 2.1.2
    • Component/s: None
    • Labels:
    • Environment:

      aws, stock cassandra or dse

      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.

        Attachments

        1. 7927-v1-die.patch
          10 kB
          John Sumsion

          Issue Links

            Activity

              People

              • Assignee:
                jdsumsion John Sumsion
                Reporter:
                jdsumsion John Sumsion
                Authors:
                John Sumsion
                Reviewers:
                Joshua McKenzie
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: