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 EF2AA10240 for ; Fri, 17 Oct 2014 00:12:52 +0000 (UTC) Received: (qmail 75950 invoked by uid 500); 17 Oct 2014 00:12:50 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 75914 invoked by uid 500); 17 Oct 2014 00:12:50 -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 75903 invoked by uid 99); 17 Oct 2014 00:12:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Oct 2014 00:12:50 +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 (athena.apache.org: domain of rcoli@eventbrite.com designates 209.85.220.181 as permitted sender) Received: from [209.85.220.181] (HELO mail-vc0-f181.google.com) (209.85.220.181) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Oct 2014 00:12:45 +0000 Received: by mail-vc0-f181.google.com with SMTP id le20so3591813vcb.12 for ; Thu, 16 Oct 2014 17:12:25 -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=KQRkx5dYoCltC/A8SrECiBVsP7n+KQ81JOU9s7lr1WM=; b=V0rv+D9d9OeZ613Fde+wpMqZKbnh6LHpurcnhM7nyRYIehBfYa80Ak/mIwU7/+QUnz rq1DGzovrQ18ObB/ojCnM1jKARlGGgOHikk17qvMBeqYQ/YAvQ7RhnLaJm6NkKO21szb ocfLe/0ZnAs7gAGja00pD5nNOzOAJj8wzXOO90vvdxIv/OwkvXSASdXlMY22B+6QMEni gxN+NcYE9wbsNIL5Uy3TgZOcAq9Dbt66R3JA5Avz8Ih6fZ6xVjleoa2SswK2btQXfEU/ WBHhB/6MdALgmjidoGrwezBTWBetWfnC8ohyjFNU7uD2/UYDc2VqyPYWMjQ+7t7YGd3T OdPQ== X-Gm-Message-State: ALoCoQntfhprjpLoFoHKrmVgLvePJ2vLTY0Wyaj9IQcdzkegLYx1IQ1xMZUX+04+VbE1USW3C7xO MIME-Version: 1.0 X-Received: by 10.221.20.198 with SMTP id qp6mr4549821vcb.18.1413504744915; Thu, 16 Oct 2014 17:12:24 -0700 (PDT) Received: by 10.31.141.213 with HTTP; Thu, 16 Oct 2014 17:12:24 -0700 (PDT) In-Reply-To: <06304502-938E-4A6C-B8DF-834306B20D4F@instructure.com> References: <06304502-938E-4A6C-B8DF-834306B20D4F@instructure.com> Date: Thu, 16 Oct 2014 17:12:24 -0700 Message-ID: Subject: Re: How to restore a snapshot in cassandra 1.1 From: Robert Coli To: "user@cassandra.apache.org" Content-Type: multipart/alternative; boundary=001a11339eb235aad30505933828 X-Virus-Checked: Checked by ClamAV on apache.org --001a11339eb235aad30505933828 Content-Type: text/plain; charset=UTF-8 On Thu, Oct 16, 2014 at 3:57 PM, Ben Chobot wrote: > We're wiping the commit logs because that's what the datastax instructions > say to do. (Also the old Cassandra Ops wiki.) I assume it's so that changes > that no longer apply to the node aren't replayed when it's restarted with > old sstables. > > Of course, my question is about when you have multiple keyspaces. > Presumably some changelogs might still apply and some might not, but AFAICT > there's no way to separate them out. > > It might just be that this kind of snapshot restore (one but not all > keyspaces) just isn't supported in Cassandra 1.1? > I told you what to do already, sorry if it was unclear : " just nodetool drain (although this doesn't actually reliably work in 1.1 era... [1]) before stopping the node. " Honestly not sure why the Datastax instructions tell you to delete the commitlog instead of using nodetool drain. I've added them (docs@ ...) to a bcc: here for their information. =Rob http://twitter.com/rcolidba --001a11339eb235aad30505933828 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= hu, Oct 16, 2014 at 3:57 PM, Ben Chobot <bench@instructure.com>= wrote:
We&#= 39;re wiping the commit logs because that's what the datastax instructi= ons say to do. (Also the old Cassandra Ops wiki.) I assume it's so that= changes that no longer apply to the node aren't replayed when it's= restarted with old sstables.

Of course, my question is = about when you have multiple keyspaces. Presumably some changelogs might st= ill apply and some might not, but AFAICT there's no way to separate the= m out.

It might just be that this kind of snapshot= restore (one but not all keyspaces) just isn't supported in Cassandra = 1.1?

I told you what to do alre= ady, sorry if it was unclear :

"=C2=A0just nod= etool drain (although this doesn't actually reliably work in 1.1 era...= [1]) before stopping the node. "

Honestly not sure why the Datastax instructions tell you to delete the com= mitlog instead of using nodetool drain. I've added them (docs@ ...) to = a bcc: here for their information.

=3D= Rob
--001a11339eb235aad30505933828--