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

Separate CorruptSSTableException and FSError handling policies

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Patch Available
    • Priority: Low
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Local/Config
    • Labels:
      None

      Description

      Currently, if disk_failure_policy is set to stop (default), StorageService will shutdown for FSError, but not CorruptSSTableException DefaultFSErrorHandler.java:40.

      But when we use policy: die, it has different behave, JVM will be killed for both FSError and CorruptSSTableException JVMStabilityInspector.java:63:

      disk_failure_policy hit FSError Exception hit CorruptSSTableException
      stop stop not stop
      die die die

      We saw CorruptSSTableException from time to time in our production, but mostly it's not because of a disk issue. So I would suggest having a separate policy for CorruptSSTable.

        Attachments

          Activity

            People

            • Assignee:
              jay.zhuang Jay Zhuang
              Reporter:
              jay.zhuang Jay Zhuang
              Authors:
              Jay Zhuang
              Reviewers:
              Jeff Jirsa
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: