Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of jbellis@gmail.com designates
 209.85.214.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CACHzRHbPwK45EGaWToJJ_LjiEck=AT0GC+5X3O=Na5x0CgM=3w@mail.gmail.com>
References: 
 <CALu7p83FvtwnfwzBPL9pwH_193Dn=U8Lc_vjpi=OAcWCMO5QFQ@mail.gmail.com>
 <CACHzRHbPwK45EGaWToJJ_LjiEck=AT0GC+5X3O=Na5x0CgM=3w@mail.gmail.com>
From: Jonathan Ellis <jbellis@gmail.com>
Date: Sat, 19 May 2012 12:12:25 -0500
Message-ID: 
 <CALdd-ziEumyXgPw+1uavbFbDtd4a7DmR4FgFpM3ieSGGCS-vPA@mail.gmail.com>
Subject: Re: Migrating a column family from one cluster to another
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Better: use bin/sstableloader, which will copy exactly the right
ranges of data to the new cluster.

On Fri, May 18, 2012 at 3:39 PM, Rob Coli <rcoli@palominodb.com> wrote:
> On Thu, May 17, 2012 at 9:37 AM, Bryan Fernandez <bfernandezsa@gmail.com> wrote:
>> What would be the recommended
>> approach to migrating a few column families from a six node cluster to a
>> three node cluster?
>
> The easiest way (if you are not using counters) is :
>
> 1) make sure all filenames of sstables are unique [1]
> 2) copy all sstablefiles from the 6 nodes to all 3 nodes
> 3) run a "cleanup" compaction on the 3 nodes
>
> =Rob
> [1] https://issues.apache.org/jira/browse/CASSANDRA-1983
>
> --
> =Robert Coli
> AIM&GTALK - rcoli@palominodb.com
> YAHOO - rcoli.palominob
> SKYPE - rcoli_palominodb


-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com