[CASSANDRA-19126] Streaming appears to be incompatible with different storage_compatibility_mode settings

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.0-rc, 5.1
• Component/s: Consistency/Streaming, Legacy/Streaming and Messaging, Messaging/Internode, Tool/bulk load
• Bug Category: Correctness - Recoverable Corruption / Loss
• Severity: Normal
• Complexity: Normal
• Discovered By: User Report
• Platform: All
• Since Version: 5.0-beta1

Source Control Link

https://github.com/apache/cassandra/commit/d422eb1f353d27264665bfe3357dac1160814ea1

Test and Documentation Plan

run regression tests, run manual tests for affected configuration

• Assignee: Jacek Lewandowski
• Reporter: Branimir Lambov

Authors

Jacek Lewandowski

Reviewers

Berenguer Blasi, Branimir Lambov

• Created: 30/Nov/23 14:25
• Updated: 23/Jan/24 15:49
• Resolved: 23/Jan/24 15:49

Description

In particular, SSTableLoader appears to be incompatible with storage_compatibility_mode: NONE, which manifests as a failure of org.apache.cassandra.distributed.test.SSTableLoaderEncryptionOptionsTest when the flag is turned on (found during CASSANDRA-18753 testing). Setting storage_compatibility_mode: NONE in the tool configuration yaml does not help (according to the docs, this setting is not picked up).

This is likely a bigger problem as the acceptable streaming version for C* 5 is 12 only in legacy mode and 13 only in none, i.e. two C* 5 nodes do not appear to be able to stream with each other if their setting for the compatibility mode is different.

Issue Links

• Discovered while testing: CASSANDRA-18753 Add an optimized default configuration to tests and make it available for new users
• relates to: CASSANDRA-19012 It should be possible to read all supported versions of sstables regardless of the compatibility mode
• links to: PR 5.0
• links to: PR trunk