[
https://issues.apache.org/jira/browse/CASSANDRA-19126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795418#comment-17795418
]
Jacek Lewandowski commented on CASSANDRA-19126:
-----------------------------------------------
[~blambov] I don't know to be honest - if we let bulkloader upload a new
sstable to the node which is still in 4.0 mode, that node will lost the ability
to downgrade. So I think it should work more or less like: if the node supports
messaging version 4.0 and 5.0, then we can stream whatever, if the node
supports messaging version 5.0, we can stream whatever, if the node supports
messaging version 4.0 we can stream only what is compatible with 4.0.
I've noticed that there is a {{correspondingMessagingVersion}} field in
{{Version}}, which is set to 4.0 for BTI (I think we should change that to 5.0)
and 3.0 for all BIG versions, which I think should be 3.0 for M, 4.0 for N and
5.0 for O. Then, the bulk loader could translate the sstable version to the
required minimum protocol version and figure out whether it can be streamed or
not.
> 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
