cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10112) Apply disk_failure_policy to transaction logs
Date Tue, 18 Aug 2015 01:16:46 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700562#comment-14700562
] 

Stefania commented on CASSANDRA-10112:
--------------------------------------

If we stashed corrupt sstable files regardless of transactions, then we would also fulfill
the requirements of CASSANDRA-9812.

> Apply disk_failure_policy to transaction logs
> ---------------------------------------------
>
>                 Key: CASSANDRA-10112
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10112
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Stefania
>            Assignee: Stefania
>
> Transaction logs were introduced by CASSANDRA-7066 and are read during start-up. In case
of file system errors, such as disk corruption, we currently log a panic error and leave the
sstable files and transaction logs as they are; this is to avoid rolling back a transaction
(i.e. deleting files) by mistake.
> We should instead look at the {{disk_failure_policy}} and refuse to start unless the
failure policy is {{ignore}}. 
> We should also consider stashing files that cannot be read during startup, either transaction
logs or sstables, by moving them to a dedicated sub-folder. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message