[ https://issues.apache.org/jira/browse/CASSANDRA-19126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795089#comment-17795089 ]
Branimir Lambov edited comment on CASSANDRA-19126 at 12/10/23 4:57 PM: ----------------------------------------------------------------------- bq. Precise fix for this would be to use the same compatibility mode for bulk loader and the node. While this would fix the test, it would not do anything about the underlying problem. C* 5 nodes in different compatibility mode should be able to stream with each other. One should at least be able to stream whole sstables from legacy mode to current. Current to legacy mode when CASSANDRA-19012 is done also makes sense, but it might violate the downgradability promise while such data is not compacted. We probably need a warning if current-format data is streamed to a node in legacy mode (e.g. suggesting one does upgradesstables before downgrading below 5.0). was (Author: blambov): > Precise fix for this would be to use the same compatibility mode for bulk > loader and the node. While this would fix the test, it would not do anything about the underlying problem. C* 5 nodes in different compatibility mode should be able to stream with each other. One should at least be able to stream whole sstables from legacy mode to current. Current to legacy mode when CASSANDRA-19012 is done also makes sense, but it might violate the downgradability promise while such data is not compacted. We probably need a warning if current-format data is streamed to a node in legacy mode (e.g. suggesting one does upgradesstables before downgrading below 5.0). > Streaming appears to be incompatible with different > storage_compatibility_mode settings > --------------------------------------------------------------------------------------- > > Key: CASSANDRA-19126 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19126 > Project: Cassandra > Issue Type: Bug > Components: Consistency/Streaming, Legacy/Streaming and Messaging, > Messaging/Internode, Tool/bulk load > Reporter: Branimir Lambov > Assignee: Jacek Lewandowski > Priority: Normal > Fix For: 5.0-rc, 5.x > > > 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. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org