cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Piotr Kołaczkowski (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6714) Upgrading from 1.2 to 2.0 without prior nodetool flush causes data loss
Date Mon, 17 Feb 2014 14:12:19 GMT

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

Piotr Kołaczkowski commented on CASSANDRA-6714:
-----------------------------------------------

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)

Mime
View raw message