Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 7 Jan 2014 18:17:51 +0000 (UTC)
From: "Michael Shuler (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12687583.1389064316994.55964.1389118671035@arcas>
In-Reply-To: <JIRA.12687583.1389064316994@arcas>
References: <JIRA.12687583.1389064316994@arcas>
Subject: [jira] [Resolved] (CASSANDRA-6554) Cluster is read-only during
 upgrade of nodes from 1.2 -> 2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Michael Shuler resolved CASSANDRA-6554.
---------------------------------------

    Resolution: Invalid

> 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)