[jira] [Updated] (CASSANDRA-9812) Handle corrupted files during startup.

["C. Scott Andreas (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-9812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

C. Scott Andreas updated CASSANDRA-9812:
----------------------------------------
    Component/s: Lifecycle

> Handle corrupted files during startup.
> --------------------------------------
>
>                 Key: CASSANDRA-9812
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9812
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Lifecycle
>         Environment: Windows-7-32 bit, 3.2GB RAM, Java 1.7.0_55
>            Reporter: Andreas Schnitzerling
>            Priority: Major
>
> This ticket is relying to CASSANDRA-9686 (refer for details). Here the conclusion: In our company we cannot avoid power-cut of the nodes (unexpected and for tests). We need a behavior, which keeps the nodes online even on finding corrupted files during startup. One idea was copy and scrub corrupted files. [~Stefania] wrote:
> {code}
> Yes a disk corruption due to a power cut could explain it. I don't think we should delete corrupt sstables though, but we could maybe move them somewhere else - where they wouldn't be automatically loaded. Then the scrub tool could copy the fixed version back into the right folder, but this is kind of opposite of what it does at the moment (save a backup and then fix the original).
> {code}
> This could avoid stopping the nodes and keep the cluster running. We need that behavior only on startup of the nodes, not during runtime. The only cause seems to be power-cut. The nodes are configured to start C* as a service.



--
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