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 A790E10B6C for ; Wed, 2 Oct 2013 00:00:39 +0000 (UTC) Received: (qmail 7221 invoked by uid 500); 2 Oct 2013 00:00:37 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 7164 invoked by uid 500); 2 Oct 2013 00:00:36 -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 7154 invoked by uid 99); 2 Oct 2013 00:00:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Oct 2013 00:00:36 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rcoli@eventbrite.com designates 209.85.216.53 as permitted sender) Received: from [209.85.216.53] (HELO mail-qa0-f53.google.com) (209.85.216.53) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Oct 2013 00:00:30 +0000 Received: by mail-qa0-f53.google.com with SMTP id k4so150184qaq.5 for ; Tue, 01 Oct 2013 17:00:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=cpn0MgDUXRg09BvBQ9X5zaKnfb+UvcPjw/65GJuU0vk=; b=VWWvWz1XAawmDvAtkvQ5x1lZ0111KChrp49Nu4lqkWDI65ll/yFatA+siyG2D3qTXE 1OJKBG11FDxpHIx/pv8XJmtNQhWfHoBWvDmVe4MEN7lXGMCRbeOP8rZ/LOoeff2WEkGk X+SzrTz44mPcQtTO+yuNUCc/wk7J0tfASKCSMmZMkQHdYQW+OqXqsrN5zaI4whHywGoj QxhPzMb40MZPXb0bbEX08SPmcYLRfITMm7NcPfCKeGgry5KosWSSr8IyypEKxEbrfumE WbRDkHcKfsEtQOrd9L+cHp1W8Mr9gOUfEabdQt0NL6Sfn5zJJsyLp1qoyh1VHbuz7VqE wopA== X-Gm-Message-State: ALoCoQk1QqCm+QuAhWLUWcbnuwZ6yQ5mozsaFPVbVb4lAbNJ2iCiuxskSWkGb/n0yRk4DYjaAQWM MIME-Version: 1.0 X-Received: by 10.224.28.201 with SMTP id n9mr14247780qac.95.1380672008994; Tue, 01 Oct 2013 17:00:08 -0700 (PDT) Received: by 10.49.67.70 with HTTP; Tue, 1 Oct 2013 17:00:08 -0700 (PDT) In-Reply-To: References: <01c601cebece$ce0c3510$6a249f30$@struq.com> Date: Tue, 1 Oct 2013 17:00:08 -0700 Message-ID: Subject: Re: Rollback question regarding system metadata change From: Robert Coli To: "user@cassandra.apache.org" Content-Type: multipart/alternative; boundary=001a11c35ab0a5d19b04e7b6c069 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c35ab0a5d19b04e7b6c069 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Oct 1, 2013 at 3:45 PM, Chris Wirt wrote: > Yep they still work. They dont acutally have any of the new system CF > created for 2.0, paxos, etc.. but they do have new rows in the > schema_columns table preventing startup and bootstrapping of new > nodes. > It *may* be least risky to manually remove these rows and then restart DC3. But unfortunately without really diving into the code, I can't make any statement about what effects it might have. > But anyway, actions to do this would be: > - drop schema (wont actually delete data?) > What actually happens is that you automatically create a snapshot in the snapshots dir when you drop, so you would have to move (or (better) hard link) those files back into place. > - create schema (will create all the metadata and leave my data > directories alone?) > - on each node run nodetool refresh (will load my existing data?) > Right. Refresh will rename all SSTables while opening them. As an alternative to refresh, you can restart the node; Cassandra loads whatever files it finds in the data dir at startup. =Rob --001a11c35ab0a5d19b04e7b6c069 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Tue, Oct 1, 2013 at 3:45 PM, Chris Wirt <chris.wirt= @struq.com> wrote:
Yep they still work. They dont acutally have= any of the new system CF
created for 2.0, paxos, etc.. but they do have new rows in the
schema_columns table preventing startup and bootstrapping of new
nodes.

It *may* be least risky to manua= lly remove these rows and then restart DC3. But unfortunately without reall= y diving into the code, I can't make any statement about what effects i= t might have.
=A0=A0
But anyway, actions to do t= his would be:
- drop schema (wont actually delete data?)

What actually happens is that you automati= cally create a snapshot in the snapshots dir when you drop, so you would ha= ve to move (or (better) hard link) those files back into place.
=A0
- create schema (will create all th= e metadata and leave my data
directories alone?)
- on each node run nodetool refresh (will load my existing data?)

Right. Refresh will rename all SSTables while op= ening them.

As an alternative to refresh, you can = restart the node; Cassandra loads whatever files it finds in the data dir a= t startup.

=3DRob


=A0
--001a11c35ab0a5d19b04e7b6c069--