You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jacek Lewandowski (Jira)" <ji...@apache.org> on 2020/07/15 07:23:00 UTC
[jira] [Created] (CASSANDRA-15946) Communication problem between C*
3 and C* 4 in in-jvm dtests
Jacek Lewandowski created CASSANDRA-15946:
---------------------------------------------
Summary: Communication problem between C* 3 and C* 4 in in-jvm dtests
Key: CASSANDRA-15946
URL: https://issues.apache.org/jira/browse/CASSANDRA-15946
Project: Cassandra
Issue Type: Bug
Components: Test/dtest
Reporter: Jacek Lewandowski
Assignee: Jacek Lewandowski
There is a communication problem when testing upgrades using in-JVM dtest between Cassandra 3 and 4.
In a method {{registerInboundFilter}} of {{Instance}}, we get a message which was just received and we prepare it for filtering as part of which, we serialize the payload again. This is fine when dealing with incoming Cassandra 4 message, because we can serialize it. However when we get the Cassandra 3 message, which uses a different protocol, and we get something like {{REQUEST_RSP}}, we can surely deserialize it through some special deserialization path, but we cannot serialize the payload for it as there is no serializer defined for {{REQUEST_RSP}} - no wonder, why would Cassandra 4.0 need to be able to serialize Cassandra 3.0 payloads?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org