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 AB13299E6 for ; Wed, 7 Mar 2012 08:13:20 +0000 (UTC) Received: (qmail 18466 invoked by uid 500); 7 Mar 2012 08:13:18 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 18440 invoked by uid 500); 7 Mar 2012 08:13:18 -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 18419 invoked by uid 99); 7 Mar 2012 08:13:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Mar 2012 08:13:18 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mccloud35@gmail.com designates 209.85.213.172 as permitted sender) Received: from [209.85.213.172] (HELO mail-yx0-f172.google.com) (209.85.213.172) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Mar 2012 08:13:11 +0000 Received: by yenm5 with SMTP id m5so3067874yen.31 for ; Wed, 07 Mar 2012 00:12:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=O4eW/OWpr/9dQsuJytVXjrSp49sAyzRv16by6DfxnP4=; b=xoTj5M9iNPbYQt9MUV/nIypBX2RBCmlJc7eKhy1YKtiJmEU2RlxG9a+XlQl/ZZVMge egYfwVkr6kHkaoe34Yu7MJLqw9A+XpkcX//womrc0Mrjo/Pn6YyxVjwWLnaYUROOdRRU 2NTDXka1vfUf1dxVUuOnl7fE/ldQzY1WLU1Zp2GAain5jigG5omCPtZcpd+K3lh6Id5W tVWyAPbCnAwMo1AYm1s/M2QCMkr+HCPK+ew3VSD1TYAsFuHsw1q3Hk/DpsitxVY2ajSa o2jorhKHyvlpWIg0vzW6rl1OSyMSil5VcrJb2jwXwOX/fw/5ShtoVDu+EcmQblQhwJq9 pW6w== MIME-Version: 1.0 Received: by 10.101.3.33 with SMTP id f33mr635601ani.80.1331107970829; Wed, 07 Mar 2012 00:12:50 -0800 (PST) Received: by 10.236.185.99 with HTTP; Wed, 7 Mar 2012 00:12:50 -0800 (PST) In-Reply-To: <7F512340-3919-4939-A205-C5A4AF8DF9F1@thelastpickle.com> References: <7F512340-3919-4939-A205-C5A4AF8DF9F1@thelastpickle.com> Date: Wed, 7 Mar 2012 13:42:50 +0530 Message-ID: Subject: Re: Repairing nodes when two schema versions appear From: Tharindu Mathew To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001636c5981bc24e6804baa2b917 X-Virus-Checked: Checked by ClamAV on apache.org --001636c5981bc24e6804baa2b917 Content-Type: text/plain; charset=ISO-8859-1 Thanks Aaron. This is great. A couple of questions if you don't mind... 1. Can this schema version issue happen in newer versions of Cassandra (>1.0) ? 2. When the node is UP and we do this, even though logs errors, still would everything come back to normal just like we shut down and delete and restart? On Wed, Mar 7, 2012 at 2:07 AM, aaron morton wrote: > Go to one of the nodes, stop it and delete the Migrations and Schema files > in the system keyspace. > > When you restart the node it will stream the migrations the other. Note > that if the node is UP and accepting traffic it may log errors about > missing CF's during this time. > > Cheers > > > ----------------- > Aaron Morton > Freelance Developer > @aaronmorton > http://www.thelastpickle.com > > On 7/03/2012, at 1:43 AM, Tharindu Mathew wrote: > > Hi, > > I try to add column families programatically and end up with 2 schema > versions in the Cassandra cluster. Using Cassandra 0.7. > > Is there a way to bring this back to normal (to one schema version) > through the cli or through the API? > > -- > Regards, > > Tharindu > > blog: http://mackiemathew.com/ > > > -- Regards, Tharindu blog: http://mackiemathew.com/ --001636c5981bc24e6804baa2b917 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks Aaron.

This is great. A couple of questions if you don't= mind...

1. Can this schema version issue happen in newer versions o= f Cassandra (>1.0) ?

2. When the node is UP and we do this, even = though logs errors, still would everything come back to normal just like we= shut down and delete and restart?

On Wed, Mar 7, 2012 at 2:07 AM, aaron morton= <aaron@the= lastpickle.com> wrote:
Go to one of the nodes, stop it and del= ete the Migrations and Schema files in the system keyspace.=A0

When you restart the node it will stream the migrations the other. N= ote that if the node is UP and accepting traffic it may log errors about mi= ssing CF's during this time.=A0

Cheers=A0


<= div style=3D"word-wrap:break-word">
-----------------
Aaron Morton
Freelance Deve= loper
@aaronmorton

On 7/03/2012, at 1:43 AM, Tharindu Mathew wrote:

Hi,

I try to add column families programatica= lly and end up with 2 schema versions in the Cassandra cluster. Using Cassa= ndra 0.7.

Is there a way to bring this back to normal (to one schema version) thr= ough the cli or through the API?

--
Regards,

Tharindu




--
Regards,

Tharindu


--001636c5981bc24e6804baa2b917--