From user-return-23902-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Thu Feb 2 20:21:08 2012 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 A65EE9084 for ; Thu, 2 Feb 2012 20:21:08 +0000 (UTC) Received: (qmail 47947 invoked by uid 500); 2 Feb 2012 20:21:06 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 47773 invoked by uid 500); 2 Feb 2012 20:21:05 -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 47765 invoked by uid 99); 2 Feb 2012 20:21:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2012 20:21:04 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [208.113.200.5] (HELO homiemail-a47.g.dreamhost.com) (208.113.200.5) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2012 20:20:56 +0000 Received: from homiemail-a47.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a47.g.dreamhost.com (Postfix) with ESMTP id 989EF28405C for ; Thu, 2 Feb 2012 12:20:35 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=thelastpickle.com; h=from :mime-version:content-type:subject:date:in-reply-to:to :references:message-id; q=dns; s=thelastpickle.com; b=CjOnWBU+bc U0VkSHiMiq/gy2uJUdcYlKN6S/cU+X2QfYefkPu28ak7QcFZDPcE3GGKqaat0oUs /GJEqnUdlj6xd29M5FGj8XUVuuGhRRunYRma+N67rusemGSmrPWTSY6W0iNbkdz4 cfeg46tVM8XTzzWszQ5AW3iWIbOFZnu2c= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thelastpickle.com; h=from :mime-version:content-type:subject:date:in-reply-to:to :references:message-id; s=thelastpickle.com; bh=lntvt4KRiDeqSKby yOAvtNBusMo=; b=W9dNrAeAK2FwzMTydEMO14R+nHS/05zjlVH57vdu2qu0zzGE WwA/zXHfpLkoKiURJSfqAJCRq7T9Ade95i0vuYbRoNjCAKDoxKZZqyYrlU1S8/Dw 5P6FO1SqfnuXoZq4PziOYOicNNy0qGFryVZNYRK1WVRaLGc3kSuyODi2xVg= Received: from [172.16.1.3] (125-236-193-159.adsl.xtra.co.nz [125.236.193.159]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aaron@thelastpickle.com) by homiemail-a47.g.dreamhost.com (Postfix) with ESMTPSA id EF07F28405B for ; Thu, 2 Feb 2012 12:20:34 -0800 (PST) From: aaron morton Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: multipart/alternative; boundary="Apple-Mail=_565A0E7A-77A4-4D74-88E3-91BC6835C8C2" Subject: Re: Using sstableloader Date: Fri, 3 Feb 2012 09:20:32 +1300 In-Reply-To: To: user@cassandra.apache.org References: Message-Id: <07C13933-6FEF-4B9D-84A9-D5312546FDF5@thelastpickle.com> X-Mailer: Apple Mail (2.1251.1) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_565A0E7A-77A4-4D74-88E3-91BC6835C8C2 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 It will make your life *a lot* easier by doing a 1 to 1 migration from = the 0.6 cluster to the 1.X one. If you want to add nodes do it once you = have 1.X happy and stable, if you need to reduce nodes threaten to hold = your breath until you pass out. =20 You can then simply: * drain and shapshot the 0.6 cluster.=20 * rsync data to the 1.X cluster and copy the configs (with necessary IP = changes etc).=20 * turn on the 1.X cluster * scrub Your roll back is to switch back the 0.6 at any time.=20 Last time I did a 0.6 upgrade I did partial migrations to the live = system so I could then do a final delta migration when the site was = down. This was done to reduce the down time when we turned the 0.6 off. = It also meant we could test the app against the 1.X cluster with stale = production data *before* the big switch over.=20 As always read the NEWS.txt for instructions, you will want to go all = the way back to the 0.7 instructions.=20 Cheers =20 ----------------- Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 3/02/2012, at 7:24 AM, Josh Behrends wrote: > I'm new to administering Cassandra so please be kind! >=20 > I've been tasked with upgrading a .6 cluster to 1.0.7. In doing this = I need a rollback plan in case things go sideways since my window for = the upgrade is fairly small. So we've decided to stand up a brand new = cluster running 1.0.7 and then stop the old cluster, snapshot the data, = and then move it over to the new cluster. =20 >=20 > So I need to know, can I use sstableloader to take the snapshot data = from my .6 cluster and stream it into my new 1.0.7 cluster? I should = also note that the new cluster MAY NOT have the same number of nodes = either. >=20 > Josh --Apple-Mail=_565A0E7A-77A4-4D74-88E3-91BC6835C8C2 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 It = will make your life *a lot*  easier by doing a 1 to 1 migration = from the 0.6 cluster to the 1.X one. If you want to add nodes do it once = you have 1.X happy and stable, if you need to reduce nodes threaten to = hold your breath until you pass out.  

You can = then simply:
* drain and shapshot the 0.6 = cluster. 
* rsync data to the  1.X cluster and copy = the configs (with necessary IP changes etc). 
* turn on = the 1.X cluster
* scrub

Your roll = back is to switch back the 0.6 at any = time. 

Last time I did a 0.6 upgrade I did = partial migrations to the live system so I could then do a final delta = migration when the site was down. This was done to reduce the down time = when we turned the 0.6 off. It also meant we could test the app against = the 1.X cluster with stale production data *before* the big switch = over. 

As always read the NEWS.txt for = instructions, you will want to go all the way back to the 0.7 = instructions. 

Cheers
 
http://www.thelastpickle.com

On 3/02/2012, at 7:24 AM, Josh Behrends wrote:

I'm new to = administering Cassandra so please be kind!

I've been = tasked with upgrading a .6 cluster to 1.0.7.  In doing this I need = a rollback plan in case things go sideways since my window for the = upgrade is fairly small.  So we've decided to stand up a brand new = cluster running 1.0.7 and then stop the old cluster, snapshot the data, = and then move it over to the new cluster.  

So I need to know, can I use sstableloader to take = the snapshot data from my .6 cluster and stream it into my new 1.0.7 = cluster?  I should also note that the new cluster MAY NOT have the = same number of nodes either.

Josh

= --Apple-Mail=_565A0E7A-77A4-4D74-88E3-91BC6835C8C2--