cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan McGuire (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-6714) Fix replaying old (1.2) commitlog in Cassandra 2.0
Date Wed, 30 Apr 2014 01:16:23 GMT

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

Ryan McGuire updated CASSANDRA-6714:
------------------------------------

    Labels: qa-resolved  (was: )

> 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
>              Labels: qa-resolved
>             Fix For: 2.0.6, 2.1 beta1
>
>         Attachments: 6714.txt
>
>
> 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.2#6252)

Mime
View raw message