cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremiah Jordan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6554) Cluster is read-only during upgrade of nodes from 1.2 -> 2.0
Date Tue, 07 Jan 2014 18:21:57 GMT

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

Jeremiah Jordan commented on CASSANDRA-6554:
--------------------------------------------

So sounds like the write failures aren't a bug.  Yes, schema changes are not supported in
a mixed cluster, so you have to run stress (or make the tables) before upgrading.

But that fact that the other nodes are shown as DOWN while doing the upgrade is an issue.
 So I would either keep this open for that, or make a new ticket for it.

> Cluster is read-only during upgrade of nodes from 1.2 -> 2.0
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-6554
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6554
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: EC2 Ubuntu Precise 12.04
> Oracle JRE 1.7_25
> C* 1.2.13 upgrade to 2.0.4
>            Reporter: Michael Shuler
>
> During an upgrade from 1.2.13 to 2.0.3/2.0.4, the cluster is read-only and writes fail,
until the entire cluster is fully upgraded.
> (I'm gathering complete repro steps, test results, and logs to try to help and will post
those asap, as well as try other versions to see what happens)



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

Mime
View raw message