[CASSANDRA-8568] Extend Transactional API to sstable lifecycle management

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.2.0 rc1
• Severity: Normal
• Assignee: Benedict Elliott Smith
• Reporter: Benedict Elliott Smith

Authors

Benedict Elliott Smith

Reviewers

Marcus Eriksson

• Created: 06/Jan/15 09:56
• Updated: 16/Apr/19 09:31
• Resolved: 22/May/15 08:47

Description

DataTracker has become a bit of a quagmire, and not at all obvious to interface with, with many subtly different modifiers. I suspect it is still subtly broken, especially around error recovery.

I propose piggy-backing on CASSANDRA-7705 to offer RAII (and GC-enforced, for those situations where a try/finally block isn't possible) objects that have transactional behaviour, and with few simple declarative methods that can be composed simply to provide all of the functionality we currently need.

See CASSANDRA-8399 for context

Issue Links

• is duplicated by: CASSANDRA-8764 Refactor the way we notify compaction strategies about early opened files
• is duplicated by: CASSANDRA-5449 Make sstable compacting status un/marking less error-prone
• is duplicated by: CASSANDRA-8506 Improve management of DataTracker, esp. compacting