[jira] [Comment Edited] (CASSANDRA-6714) Upgrading from 1.2 to 2.0 without prior nodetool flush causes data loss

["Piotr Kołaczkowski (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-6714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903258#comment-13903258 ] 

Piotr Kołaczkowski edited comment on CASSANDRA-6714 at 2/17/14 2:11 PM:
------------------------------------------------------------------------

Discovered while testing CASSANDRA-6707.

{quote}
However, I will note that after upgrading the first node to 2.0, the results of select count(*) were consistent but incorrect (I got 957815 as the result). After upgrading the second node to 2.0 I got another consistent but incorrect result (912873).
{quote}


was (Author: pkolaczk):
Discovered while testing CASSANDRA-6707.

> Upgrading from 1.2 to 2.0 without prior nodetool flush causes data loss
> -----------------------------------------------------------------------
>
>                 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
>            Priority: Critical
>
> 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.



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