[CASSANDRA-5079] Compaction deletes ExpiringColumns in Secondary Indexes

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 1.1.9, 1.2.0 rc2
• Component/s: Feature/2i Index
• Severity: Normal
• Assignee: Aaron Morton Assign to me
• Reporter: Aaron Morton

Authors

Aaron Morton

Reviewers

Sylvain Lebresne

• Created: 20/Dec/12 04:05
• Updated: 16/Apr/19 09:32
• Resolved: 20/Dec/12 09:12

Description

From this discussion http://www.mail-archive.com/[e-mail]/msg26599.html

CompactionManager.getDefaultGcBefore() set's the gc_before to be Integer.MAX_VALUE.

In the example all entries in the secondary index have a TTL. In PreCompactedRow.removeDeletedAndOldShards() the CF is determined to have irrelevant data, the call to CFS.removeDeleted() results in the ExpiringColumns being removed and the row is treated as empty. CompactionTask.execute() exits at the if (!nni.hasNext()) test, so the sstables are marked as compacted and soon deleted.

In the example the localDeletionTime was Thu, 21 Mar 2013 08:25:22 GMT and should not have been purged.

In the example when the first compaction on the secondary index runs the on disk data for the index is deleted. The logs show a compaction starting and no associated "Compacted to" message from that compaction thread.

The impact is incorrect results from secondary indexes queries.

Issue Links

• duplicates: CASSANDRA-5024 Secondary Index seen as empty
• is related to: CASSANDRA-4670 LeveledCompaction destroys secondary indexes