Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 24 Sep 2014 22:44:34 +0000 (UTC)
From: "Yeshvanthni (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12743812.1411578836000.116455.1411598674681@Atlassian.JIRA>
In-Reply-To: <JIRA.12743812.1411578836000@Atlassian.JIRA>
References: <JIRA.12743812.1411578836000@Atlassian.JIRA>
 <JIRA.12743812.1411578836627@arcas>
Subject: [jira] [Comment Edited] (CASSANDRA-8000) Schema Corruption when
 1.2.15->2.0.9 rolling upgrade and in mixed mode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Yeshvanthni edited comment on CASSANDRA-8000 at 9/24/14 10:44 PM:
------------------------------------------------------------------

Wait for a while in mixed mode and query against 1.2.15 node in the cluster. 2.0.9 nodes return fine.


was (Author: yeshvanthni):
Wait for a while in mixed mode and query against 1.2.15 node in the cluster. 2.0.9 no
des return fine.

> Schema Corruption when 1.2.15->2.0.9 rolling upgrade and in mixed mode
> ----------------------------------------------------------------------
>
>                 Key: CASSANDRA-8000
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8000
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Yeshvanthni
>
> Steps to reproduce:
> 1. Setup multi-node Cassandra 1.2.15 with following schema 
> {code}
> CREATE KEYSPACE testkeyspace WITH replication = {
>   'class': 'SimpleStrategy',
>   'replication_factor':2
> };
> USE testkeyspace;
> CREATE TABLE test (
>   testid timeuuid PRIMARY KEY,
>   businesskey timestamp,
>   createdby text,
>   createdtimestamp timestamp,
>   testname text
> ) ;
> insert into test(testid,businesskey,createdby,createdtimestamp,testname) VALUES (now(),dateOf(now()),'user',dateOf(now()),'test');
> {code}
> 2. Roll one node to Cassandra 2.0.9 
>          - Snapshot 1.2.15 
>          - Decommission the old 1.2.15
>          - Start Cassandra 2.0.9 pointing to the same data folder  as 1.2.15
>          - nodetool upgradesstables 
> 3. Query against 1.2.15 nodes of the cluster with CQLSH
> It returns an additional primary key column with null value in it. Describe shows that the table has somehow got the additional column
> {code}
> CREATE TABLE test (
>   testid timeuuid PRIMARY KEY,
>   testid timeuuid,
>   businesskey timestamp,
>   createdby text,
>   createdtimestamp timestamp,
>   testname text
> ) ;
> {code}
> Observation:
> This could be because of the change in Cassandra 2.x to store all columns including the key columns in schema_columns while earlier key columns were stored schema_columnfamilies.
> This blocks rolling upgrades and fails the cluster when in mixed mode.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)