[ https://issues.apache.org/jira/browse/CASSANDRA-6503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852019#comment-13852019 ]
Jeremiah Jordan commented on CASSANDRA-6503: -------------------------------------------- One thing I was thinking that might help with this is if we could leave the sstables named "-tmp" until we are ready to make them become active. That way when you reboot, any files hanging around will get removed on restart, instead of becoming active. > sstables from stalled repair sessions become live after a reboot and can > resurrect deleted data > ----------------------------------------------------------------------------------------------- > > Key: CASSANDRA-6503 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6503 > Project: Cassandra > Issue Type: Bug > Reporter: Jeremiah Jordan > > The sstables streamed in during a repair session don't become active until > the session finishes. If something causes the repair session to hang for > some reason, those sstables will hang around until the next reboot, and > become active then. If you don't reboot for 3 months, this can cause data to > resurrect, as GC grace has expired, so tombstones for the data in those > sstables may have already been collected. -- This message was sent by Atlassian JIRA (v6.1.4#6159)