[ https://issues.apache.org/jira/browse/CASSANDRA-19126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795225#comment-17795225 ]
Jacek Lewandowski commented on CASSANDRA-19126: ----------------------------------------------- My understanding of the upgrade process is as follows: # Start the cluster with the SCM = 4, all the nodes produce and accept only 4.0 sstable # When the user decides to upgrade, do the rolling restart of the nodes with SCM = UPGRADE, from this moment, all the nodes should still produce old sstables, but they should start accepting new sstables for streaming # Start the rolling restart with SCM = NONE, from this moment, some nodes starts to produce new sstables and try to stream them to other nodes, those other nodes should accept them. TBH, I don't understand the need to have two modes: 4 and UPGRADE. If both produce only old sstables, none of the node would produce a new sstable which will retain the ability to downgrade. Though, this should be addressed in CASSANDRA-19012. In this ticket the issue was the fact that the tool used wrong configuration. > 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