[ https://issues.apache.org/jira/browse/CASSANDRA-6503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-6503: -------------------------------------- Priority: Minor (was: Major) Fix Version/s: (was: 1.2.14) 2.0.4 (Not actually sure this is still an issue in 2.0.x but it seems possible.) > 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 > Assignee: Yuki Morishita > Priority: Minor > Fix For: 2.0.4 > > > 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)