[jira] [Updated] (CASSANDRA-7377) Should be an option to fail startup if corrupt SSTable found

2018-02-14 Thread Jeff Jirsa (JIRA)

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

Jeff Jirsa updated CASSANDRA-7377:
--
Labels:   (was: proposed-wontfix)

> 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
>Priority: Major
>
> 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
(v7.6.3#76005)

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



[jira] [Updated] (CASSANDRA-7377) Should be an option to fail startup if corrupt SSTable found

2017-12-11 Thread Jeff Jirsa (JIRA)

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

Jeff Jirsa updated CASSANDRA-7377:
--
Labels: proposed-wontfix  (was: )

> 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
>  Labels: proposed-wontfix
>
> 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.4.14#64029)

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