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

Posted to commits@cassandra.apache.org by "Stefan Podkowinski (JIRA)" <ji...@apache.org> on 2019/01/22 12:23:00 UTC

[jira] [Created] (CASSANDRA-14993) Catch CorruptSSTableExceptions and FSErrors in ALAExecutorService

Stefan Podkowinski created CASSANDRA-14993:
----------------------------------------------

             Summary: Catch CorruptSSTableExceptions and FSErrors in ALAExecutorService
                 Key: CASSANDRA-14993
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14993
             Project: Cassandra
          Issue Type: Bug
            Reporter: Stefan Podkowinski
            Assignee: Stefan Podkowinski
             Fix For: 2.2.x, 3.0.x, 3.11.x, 4.0.x


Actively handling CorruptSSTableExceptions and FSErrors currently only happens during opening of sstables and in the default exception handler. What's missing is to catch these in AbstractLocalAwareExecutorService as well. Therefor I propose to add calls to FileUtils.handleCorruptSSTable/handleFSError there, too, so we don't miss invoking the disk failure policy in that case.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org