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/02/04 15:49:00 UTC
[jira] [Updated] (CASSANDRA-14993) Catch CorruptSSTableExceptions and FSErrors in ALAExecutorService
[ https://issues.apache.org/jira/browse/CASSANDRA-14993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Podkowinski updated CASSANDRA-14993:
-------------------------------------------
Resolution: Fixed
Fix Version/s: (was: 4.0.x)
(was: 3.11.x)
(was: 3.0.x)
4.0
3.11.5
3.0.19
Status: Resolved (was: Ready to Commit)
Thanks, Ariel!
Merged as c94a6aa7e5dd6d to cassandra-3.0
Tests CircleCI:
[3.0|https://circleci.com/workflow-run/f8154177-162a-416e-ad79-4c3c86f66906]
[3.11|https://circleci.com/workflow-run/eaaf37f8-ea9e-4a0a-b138-c26855e44309]
[trunk|https://circleci.com/workflow-run/76cab84e-33f8-45b8-ba4a-2d5ba8fa37a3]
> 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
> Priority: Major
> Fix For: 3.0.19, 3.11.5, 4.0
>
>
> 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