cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sankalp kohli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6756) Provide option to avoid loading orphan SSTables on startup
Date Tue, 25 Feb 2014 02:28:20 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911146#comment-13911146
] 

sankalp kohli commented on CASSANDRA-6756:
------------------------------------------

Since json manifest is out, we can store the stable number in system table before making it
live. That way we can avoid picking any stable that is not suppose to be live. 

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

Mime
View raw message