[
https://issues.apache.org/jira/browse/CASSANDRA-7377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14027569#comment-14027569
]
Richard Low commented on CASSANDRA-7377:
----------------------------------------
This has the same affect as in CASSANDRA-6696 but a different cause so probably
a different patch.
> 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)
