Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <4F70EE46.1090805@syncopated.net>
References: <4F70BFB4.9070308@syncopated.net>
	<4F5BD801-9D97-482D-8FE8-E0802B213DC7@thelastpickle.com>
	<4F70EE46.1090805@syncopated.net>
Date: Mon, 2 Apr 2012 10:42:02 -0700
Message-ID: 
 <CACHzRHYs2DwYof_Y9XsZ4GJbUSr0iJACq8tmaCOW7k82pFw20Q@mail.gmail.com>
Subject: Re: multi region EC2
From: Rob Coli <rcoli@palominodb.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Mar 26, 2012 at 3:31 PM, Deno Vichas > but what if i already
have a bunch (8g per node) data that i need and i
> don't have a way to re-create it.

Note that the below may have unintended consequences if using Counter
column families. It actually can be done with the cluster running,
below is the least tricky version of this process.

a) stop writing to your cluster
b) do a major compaction and then stop cluster
c) ensure globally unique filenames for all sstable files for all cfs
for all nodes
d) copy all sstables to all new nodes
e) start cluster, join new nodes, run cleanup compactions

=Rob

-- 
=Robert Coli
AIM&GTALK - rcoli@palominodb.com
YAHOO - rcoli.palominob
SKYPE - rcoli_palominodb