Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D7C4AD771 for ; Wed, 5 Sep 2012 21:40:13 +0000 (UTC) Received: (qmail 96283 invoked by uid 500); 5 Sep 2012 21:40:09 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 96239 invoked by uid 500); 5 Sep 2012 21:40:09 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 96229 invoked by uid 99); 5 Sep 2012 21:40:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Sep 2012 21:40:08 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Edward.Sargisson@globalrelay.net designates 208.81.212.160 as permitted sender) Received: from [208.81.212.160] (HELO ex1.globalrelay.net) (208.81.212.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Sep 2012 21:40:03 +0000 Received: from [10.5.5.212] (208.81.212.224) by ex1.office.globalrelay.net (10.6.60.10) with Microsoft SMTP Server id 8.1.436.0; Wed, 5 Sep 2012 14:39:43 -0700 Message-ID: <5047C69F.9040606@globalrelay.net> Date: Wed, 5 Sep 2012 14:39:43 -0700 From: Edward Sargisson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Subject: Re: Schema Disagreement after migration from 1.0.6 to 1.1.4 References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------060105040204060300050000" X-Virus-Checked: Checked by ClamAV on apache.org --------------060105040204060300050000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit I would try nodetool resetlocalschema. On 12-09-05 07:08 AM, Martin Koch wrote: > Hi list > > We have a 5-node Cassandra cluster with a single 1.0.9 installation > and four 1.0.6 installations. > > We have tried installing 1.1.4 on one of the 1.0.6 nodes (following > the instructions on http://www.datastax.com/docs/1.1/install/upgrading). > > After bringing up 1.1.4 there are no errors in the log, but the > cluster now suffers from schema disagreement > > [default@unknown] describe cluster; > Cluster Information: > Snitch: org.apache.cassandra.locator.SimpleSnitch > Partitioner: org.apache.cassandra.dht.RandomPartitioner > Schema versions: > 59adb24e-f3cd-3e02-97f0-5b395827453f: [10.10.29.67] <-The new 1.1.4 node > > 943fc0a0-f678-11e1-0000-339cf8a6c1bf: [10.10.87.228, 10.10.153.45, > 10.10.145.90, 10.38.127.80] <- nodes in the old cluster > > The recipe for recovering from schema disagreement > (http://wiki.apache.org/cassandra/FAQ#schema_disagreement) doesn't > cover the new directory layout. The system/Schema directory is empty > save for a snapshots subdirectory. system/schema_columnfamilies and > system/schema_keyspaces contain some files. As described in datastax's > description, we tried running nodetool upgradesstables. When this had > done, describe schema in the cli showed a schema definition which > seemed correct, but was indeed different from the schema on the other > nodes in the cluster. > > Any clues on how we should proceed? > > Thanks, > /Martin Koch -- Edward Sargisson senior java developer Global Relay edward.sargisson@globalrelay.net *866.484.6630* New York | Chicago | Vancouver | London (+44.0800.032.9829) | Singapore (+65.3158.1301) Global Relay Archive supports email, instant messaging, BlackBerry, Bloomberg, Thomson Reuters, Pivot, YellowJacket, LinkedIn, Twitter, Facebook and more. Ask about *Global Relay Message* *--- *The Future of Collaboration in the Financial Services World * *All email sent to or from this address will be retained by Global Relay's email archiving system. This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. Global Relay will not be liable for any compliance or technical information provided herein. All trademarks are the property of their respective owners. --------------060105040204060300050000 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit I would try nodetool resetlocalschema.


On 12-09-05 07:08 AM, Martin Koch wrote:
Hi list

We have a 5-node Cassandra cluster with a single 1.0.9 installation and four 1.0.6 installations. 

We have tried installing 1.1.4 on one of the 1.0.6 nodes (following the instructions on http://www.datastax.com/docs/1.1/install/upgrading).

After bringing up 1.1.4 there are no errors in the log, but the cluster now suffers from schema disagreement

[default@unknown] describe cluster;
Cluster Information:
   Snitch: org.apache.cassandra.locator.SimpleSnitch
   Partitioner: org.apache.cassandra.dht.RandomPartitioner
   Schema versions: 
59adb24e-f3cd-3e02-97f0-5b395827453f: [10.10.29.67] <- The new 1.1.4 node

943fc0a0-f678-11e1-0000-339cf8a6c1bf: [10.10.87.228, 10.10.153.45, 10.10.145.90, 10.38.127.80] <- nodes in the old cluster

The recipe for recovering from schema disagreement (http://wiki.apache.org/cassandra/FAQ#schema_disagreement) doesn't cover the new directory layout. The system/Schema directory is empty save for a snapshots subdirectory. system/schema_columnfamilies and system/schema_keyspaces contain some files. As described in datastax's description, we tried running nodetool upgradesstables. When this had done, describe schema in the cli showed a schema definition which seemed correct, but was indeed different from the schema on the other nodes in the cluster. 

Any clues on how we should proceed?

Thanks,
/Martin Koch

--

Edward Sargisson

senior java developer
Global Relay

edward.sargisson@globalrelay.net


866.484.6630 
New York | Chicago | Vancouver  |  London  (+44.0800.032.9829)  |  Singapore  (+65.3158.1301)

Global Relay Archive supports email, instant messaging, BlackBerry, Bloomberg, Thomson Reuters, Pivot, YellowJacket, LinkedIn, Twitter, Facebook and more. 


Ask about Global Relay Message — The Future of Collaboration in the Financial Services World


All email sent to or from this address will be retained by Global Relay’s email archiving system. This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law.  Global Relay will not be liable for any compliance or technical information provided herein.  All trademarks are the property of their respective owners.

--------------060105040204060300050000--