You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Richard Low (JIRA)" <ji...@apache.org> on 2014/06/11 11:20:02 UTC
[jira] [Created] (CASSANDRA-7377) Should be an option to fail
startup if corrupt SSTable found
Richard Low created CASSANDRA-7377:
--------------------------------------
Summary: Should be an option to fail startup if corrupt SSTable found
Key: CASSANDRA-7377
URL: https://issues.apache.org/jira/browse/CASSANDRA-7377
Project: Cassandra
Issue Type: Improvement
Reporter: Richard Low
We had a server that crashed and when it came back, some SSTables were corrupted. Cassandra happily started, but we then realised the corrupt SSTable contained some tombstones and a few keys were resurrected. This means corruption on a single replica can bring back data even if you run repairs at least every gc_grace.
There should be an option, probably controlled by the disk failure policy, to catch this and stop node startup.
--
This message was sent by Atlassian JIRA
(v6.2#6252)