[CASSANDRA-19744] Accord migration and interop correctness

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Component/s: Accord
• Labels: pull-request-available
• Epic Link: CEP-15: Accord Beta
• Platform: All
• Assignee: Ariel Weisberg
• Reporter: Ariel Weisberg

Authors

Ariel Weisberg

Reviewers

Blake Eggleston

• Created: 02/Jul/24 14:59
• Updated: 22/Aug/24 21:35
• Resolved: 14/Aug/24 17:16

Description

There are several issues around splitting and retrying mutations, using the original timestamp for batchlog/hints, batchlog/hint support in general, running Accord barriers only against the ranges actually owned by Accord.

Issue Links

• fixes: CASSANDRA-19430 Read repair through Accord needs to only route the read repair through Accord if the range is actually migrated/running on Accord
• fixes: CASSANDRA-19434 Batch log doesn't write through Accord during Accord migration
• fixes: CASSANDRA-19435 Hint delivery doesn't write through Accord
• fixes: CASSANDRA-19438 Accord barriers need to handle racing with topology changes
• fixes: CASSANDRA-19440 Non-serial writes can race with Accord topology changes
• fixes: CASSANDRA-19736 Batchlog and hint replay have timestamps replaced by Accord
• fixes: CASSANDRA-19431 Mutations need to split Accord/non-Accord mutations based on whether migration is completed
• links to: Accord PR
• links to: Cassandra PR