[ https://issues.apache.org/jira/browse/CASSANDRA-6503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868182#comment-13868182 ]
Jason Brown commented on CASSANDRA-6503: ---------------------------------------- bq. call SSTW.abort() ... Makes sense, will add that in. bq. If the node goes down during we are doing closeAndOpenReader to received files, there is a chance we have already renamed files Ok, got it. Will come up with an idea and drop into the next patch. Thanks > 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: Jason Brown > Priority: Minor > Fix For: 1.2.14, 2.0.5 > > Attachments: 6503_c1.2-v1.patch > > > 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.5#6160)