[jira] [Commented] (CASSANDRA-10112) Refuse to start and print txn log information in case of disk corruption

["Marcus Eriksson (JIRA)" <ji...@apache.org>]

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

Marcus Eriksson commented on CASSANDRA-10112:
---------------------------------------------

Does anyone remember why we didn't commit this to 3.0 as well?

> Refuse to start and print txn log information in case of disk corruption
> ------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10112
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10112
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local Write-Read Paths
>            Reporter: Stefania
>            Assignee: Stefania
>              Labels: doc-impacting
>             Fix For: 3.6
>
>
> 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.4.14#64029)

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