[CASSANDRA-19872] Handle losing CMS status while committing a transformation

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.x
• Component/s: Transactional Cluster Metadata
• Bug Category: Degradation - Other Exception
• Severity: Low
• Complexity: Normal
• Discovered By: Fuzz Test
• Platform: All
• Since Version: NA

Source Control Link

https://github.com/apache/cassandra/commit/6dc9ca99fa7eb2ca2e1ea841f5566c3fb5d3f864

Test and Documentation Plan

testing in https://issues.apache.org/jira/browse/CASSANDRA-19847

• Assignee: Marcus Eriksson
• Reporter: Marcus Eriksson

Authors

Marcus Eriksson

Reviewers

David Capwell, Sam Tunnicliffe

• Created: 27/Aug/24 12:26
• Updated: 04/Sep/24 13:41
• Resolved: 04/Sep/24 13:41

Description

There is a small window where we might try to use the wrong processor when committing a transformation while the CMS changes - in this case we should just retry the commit and we'll use the RemoteProcessor

Issue Links

• blocks: CASSANDRA-19847 Create a fuzz test that randomizes topology changes, cluster actions, and CQL operations
• links to: GitHub Pull Request #3502