[
https://issues.apache.org/jira/browse/CASSANDRA-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910074#comment-13910074
]
Vincent Mallet commented on CASSANDRA-6756:
-------------------------------------------
Any kind, really. The stalled repair problem hit us pretty massively on a
recent cluster bounce, and I'm thinking "who knows what other problem or other
bug is going to leave orphan SSTables behind". Fair enough there shouldn't be
any, but the day there are it's not worth us paying the price of zombie data.
We're also thinking of grabbing that patch and porting it to 1.1 while we're on
it until we migrate to 1.2. The default behavior of sucking in any SSTables
that are laying around is just making us very nervous.
Hope that makes sense, thanks.
> Provide option to avoid loading orphan SSTables on startup
> ----------------------------------------------------------
>
> Key: CASSANDRA-6756
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6756
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Vincent Mallet
> Fix For: 1.2.16
>
>
> When Cassandra starts up, it enumerates all SSTables on disk for a known
> column family and proceeds to loading all of them, even those that were left
> behind before the restart because of a problem of some sort. This can lead to
> "data gain" (resurrected data) which is just as bad as data loss.
> The ask is to provide a yaml config option which would allow one to turn that
> behavior off by default so a cassandra cluster would be immune to data gain
> when nodes get restarted (at least with Leveled where Cassandra keeps track
> of SSTables).
> This is sort of a follow-up to CASSANDRA-6503 (fixed in 1.2.14). We're just
> extremely nervous that orphan SSTables could appear because of some other
> potential problem somewhere else and cause zombie data on a random reboot.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
