[CASSANDRA-1015] Internal Messaging should be backwards compatible

• Type: Improvement
• Status: Resolved
• Priority: Urgent
• Resolution: Fixed
• Fix Version/s: 0.8 beta 1
• Assignee: Gary Dusbabek
• Reporter: Ryan King

Authors

Gary Dusbabek

• Created: 23/Apr/10 05:19
• Updated: 16/Apr/19 09:33
• Resolved: 07/Feb/11 15:48

Description

Currently, incompatible changes in the node-to-node communication prevent rolling restarts of clusters.

In order to fix this we should:

1) use a framework that makes doing compatible changes easy
2) have a policy of only making compatible changes between versions n and n+1*

• Running multiple versions should only be supported for small periods of time. Running clusters of mixed version is not needed here.

Issue Links

• is related to: CASSANDRA-2018 drop messages from the future.
• relates to: CASSANDRA-1765 Compare serialization metrics between a few frameworks.

Sub-Tasks

• unit tests that validate that message serialization isn't broken in the current version.: Resolved
• Disambiguate messages from different versions of cassandra.: Resolved
• Message version resolution: Resolved
• Message translation: Resolved