[CASSANDRA-19288] Accord: Asynchronous reads may be unsafe

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.1-alpha1
• Component/s: Accord
• Epic Link: CEP-15: General Purpose Transactions
• Change Category: Quality Assurance
• Complexity: Normal
• Platform: All

Source Control Link

https://github.com/apache/cassandra-accord/commit/527094c69ad23319b058917b1c8974d01c5d86e6

Test and Documentation Plan

ci

• Assignee: Blake Eggleston
• Reporter: Benedict Elliott Smith

Authors

Blake Eggleston

Reviewers

David Capwell

• Created: 23/Jan/24 16:04
• Updated: 18/Jun/24 18:10
• Resolved: 18/Jun/24 18:10

Description

In principle we should invalidate asynchronous reads before they complete if the data they read may be invalid, but this anyway causes faults when we permit them to occur in accord-core. We can and perhaps should simply ensure the reads are issued against an sstable/memtable snapshot taken by the command store, as this is lower cost and more robust. Otherwise we should investigate what issue asynchronous reads cause.