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 C5218D6F1 for ; Wed, 5 Sep 2012 14:08:42 +0000 (UTC) Received: (qmail 84453 invoked by uid 500); 5 Sep 2012 14:08:40 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 84391 invoked by uid 500); 5 Sep 2012 14:08:40 -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 84382 invoked by uid 99); 5 Sep 2012 14:08:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Sep 2012 14:08:40 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.220.172] (HELO mail-vc0-f172.google.com) (209.85.220.172) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Sep 2012 14:08:33 +0000 Received: by vcbfo14 with SMTP id fo14so957255vcb.31 for ; Wed, 05 Sep 2012 07:08:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=maVVO9Y+XIiBCmGzHKopG3aLn9CUcnwX38trXH5pjjA=; b=T0m80heghaksgjTxxH4T5QaYA2oW4MfGGZ2zm+G3lwsOos/DzoK5jYSjiBCELgzG63 +zVt+69jMpxjtXliJsM/oLsODMPM+jWgWhBusV7Uzfn+wkES/TLzjDT7ThSL8i2a5BSD lWRW60URwTLC2+FmjqonDQCl6id7HAWEeSQUhucSUrTi5+eIXvH5KGWgFrTSeDwM9wgW 4dnASPlgsAU8BOdfVQ+lzIiwvFlrK0UaaBVR+kuwyJ/iwoSX55K+sQ/bEpW+GBh6J4DL wB5cfwEBWKPe+bbCbT3M9FgIi96YIcPo5NVu4FwcLtzOtLPKL9/OSjxDfVtRbfDPhwK4 jfAg== MIME-Version: 1.0 Received: by 10.220.223.202 with SMTP id il10mr2634654vcb.2.1346854092370; Wed, 05 Sep 2012 07:08:12 -0700 (PDT) Received: by 10.58.227.5 with HTTP; Wed, 5 Sep 2012 07:08:12 -0700 (PDT) Date: Wed, 5 Sep 2012 16:08:12 +0200 Message-ID: Subject: Schema Disagreement after migration from 1.0.6 to 1.1.4 From: Martin Koch To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=14dae9cdc487bd725604c8f4e736 X-Gm-Message-State: ALoCoQkvNbWMNdUZAW6m3SrAakPP2sDRAZmwMCnCxzEnVNAheg0WFxmfnHgtiJCG1dcwrNxdci+j --14dae9cdc487bd725604c8f4e736 Content-Type: text/plain; charset=ISO-8859-1 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 --14dae9cdc487bd725604c8f4e736 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi list

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

We have tried installing 1.1.4 on one of the 1.0.6 nodes (following the = instructions on=A0http://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

<= div>
[default@unknown] describe c= luster;
Cluster Information:
=A0 =A0Snitch: org.apache.cassa= ndra.locator.SimpleSnitch
=A0 =A0Partitioner: org.apache.cassandra.dht.RandomPartitioner=
=A0 =A0Schema versions:=A0
59adb24e-f3cd-3e02-97f0-5b395827453= f: [10.10.29.67] <- T= he new 1.1.4 node

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

The recipe for recovering from schema disagreemen= t (htt= p://wiki.apache.org/cassandra/FAQ#schema_disagreement) doesn't cove= r the new directory layout. The system/Schema directory is empty save for a= snapshots subdirectory. system/schema_columnfamilies and system/schema_key= spaces contain some files. As described in datastax's description, we t= ried 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.=A0

Any clues on how we should proceed?

Thanks,
/Martin Koch
--14dae9cdc487bd725604c8f4e736--