[
https://issues.apache.org/jira/browse/CASSANDRA-6503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13853475#comment-13853475
]
Yuki Morishita commented on CASSANDRA-6503:
-------------------------------------------
In 1.2 as well as 2.0, every time the node receives SSTable file, it starts
writing as 'tmp', but at the end of receiving, it calls
SSTableWriter#closeAndOpenReader that moves received file out of 'tmp'. At this
point, SSTables are still not added to ColumnFamilyStore, though if we shutdown
the node and restart, the node would recognize received files even though
streaming session was not finished successfully.
We need little tweak to defer renaming of SSTable files to do so after
receiving all streamed files.
> 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.5
>
>
> 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)
