[CASSANDRA-6503] sstables from stalled repair sessions become live after a reboot and can resurrect deleted data

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 1.2.14, 2.0.5
• Severity: Low
• Since Version: 0.7.0
• Assignee: Jason Brown
• Reporter: Jeremiah Jordan

Authors

Jason Brown

Reviewers

Yuki Morishita

• Created: 18/Dec/13 18:52
• Updated: 16/Apr/19 09:31
• Resolved: 31/Jan/14 13:31

Description

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.

Issue Links

• is related to: CASSANDRA-5412 Lots of deleted rows came back to life after upgrade from 1.1.6 to 1.1.10
• is related to: CASSANDRA-6756 Provide option to avoid loading orphan SSTables on startup
• relates to: CASSANDRA-10797 Bootstrap new node fails with OOM when streaming nodes contains thousands of sstables