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

["Aleksey Yeschenko (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko updated CASSANDRA-6714:
-----------------------------------------

    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.

  was:Accidentally forgetting to nodetool drain or flush before upgrading to 2.0  causes silent loss of unflushed data. No errors or warnings are reported in the system.log.

       Priority: Major  (was: Critical)
        Summary: Fix replaying old (1.2) commitlog in Cassandra 2.0  (was: Upgrading from 1.2 to 2.0 without prior nodetool flush causes data loss)

> Fix replaying old (1.2) commitlog in Cassandra 2.0
> --------------------------------------------------
>
>                 Key: CASSANDRA-6714
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6714
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Old node: Cassandra 1.2.15 (DSE)
> New node: Cassandra 2.0.5.1 (DSE)
>            Reporter: Piotr Kołaczkowski
>            Assignee: Aleksey Yeschenko
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)