[CASSANDRA-13944] Throw descriptive errors for mixed mode repair attempts

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 4.0-alpha1, 4.0
• Component/s: Consistency/Repair
• Severity: Low
• Assignee: Blake Eggleston Assign to me
• Reporter: Blake Eggleston

Authors

Blake Eggleston

Reviewers

Marcus Eriksson

• Created: 09/Oct/17 22:22
• Updated: 21/Jan/21 20:19
• Resolved: 24/Oct/17 20:56

Description

We often make breaking changes to streaming and repair between major versions, and don't usually support either in mixed mode clusters. Streaming connections check protocol versions, but repair message handling doesn't, which means cryptic exceptions show up in the logs when operators forget to turn off whatever's scheduling repairs on their cluster. Refusing to send or receive repair messages to/ from incompatible messaging service versions, and throwing a descriptive exception would make it clearer why repair is not working, as well as prevent any potentially unexpected behavior.

Issue Links

• relates to: CASSANDRA-16244 Create a jvm upgrade dtest for mixed versions repairs