[CASSANDRA-6714] Fix replaying old (1.2) commitlog in Cassandra 2.0

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.0.6, 2.1 beta1
• Labels: qa-resolved

Environment

Old node: Cassandra 1.2.15 (DSE)
New node: Cassandra 2.0.5.1 (DSE)

• Severity: Normal
• Assignee: Aleksey Yeschenko
• Reporter: Piotr Kolaczkowski

Authors

Aleksey Yeschenko

Reviewers

Jonathan Ellis

• Tester: Ryan McGuire
• Created: 17/Feb/14 14:08
• Updated: 16/Apr/19 09:31
• Resolved: 18/Feb/14 22:41

Description

Our docs, and code, both explicitly say that you should drain a node before upgrading to a new major release.

If you don't do what the docs explicitly tell you to do, however, Cassandra won't scream at you. Also, we do currently have logic to replay 1.2 commitlog in 2.0, but it seems to be slightly broken, unfortunately.

Issue Links

• is related to: CASSANDRA-5199 Avoid serializing to byte[] on commitlog append