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 3506410817 for ; Wed, 10 Jul 2013 17:07:40 +0000 (UTC) Received: (qmail 8074 invoked by uid 500); 10 Jul 2013 17:07:37 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 8053 invoked by uid 500); 10 Jul 2013 17:07: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 8045 invoked by uid 99); 10 Jul 2013 17:07:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jul 2013 17:07: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 (athena.apache.org: domain of baskar.duraikannu.db@gmail.com designates 209.85.212.174 as permitted sender) Received: from [209.85.212.174] (HELO mail-wi0-f174.google.com) (209.85.212.174) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jul 2013 17:07:32 +0000 Received: by mail-wi0-f174.google.com with SMTP id k10so11659972wiv.13 for ; Wed, 10 Jul 2013 10:07:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Eysp9BiOzMWhNY9v2E85g7eT3Ct16I8zM928IOJgiBA=; b=eY3t6RZGSS9ukUZHfqKHc07K7m6il/o5Qz8IaYSvgioqeaNOT9gun9c2SkLYxEDiZA UjhiLtVbJHSDwa+e/PEKy//LuqCHGXFFc1F6NRMG5TlNBtbANb6apMqDtZaS9KVKLo+S NyrG88GPEJuZnb8LWyCnp2037Q3XzzUoCmGbYwp+z8d0CugtqO3DIgF6bqe1DE8vBZIg KKQ5pK0jPedYs9kHOj6rgw32xSPDjL3/2j3jNuvynZwP8S3AwAhUZAj2LGaV3ej/8U8n biGo1GQxPb0WuEQ6NkRtSTui/D+vSL/magOSAJ8rLL8cr0PpLx5lIEglaF9LRnqxyVjp dO2A== MIME-Version: 1.0 X-Received: by 10.180.10.168 with SMTP id j8mr17598245wib.15.1373476030314; Wed, 10 Jul 2013 10:07:10 -0700 (PDT) Received: by 10.216.192.195 with HTTP; Wed, 10 Jul 2013 10:07:10 -0700 (PDT) In-Reply-To: References: Date: Wed, 10 Jul 2013 13:07:10 -0400 Message-ID: Subject: Re: Node tokens / data move From: Baskar Duraikannu To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a11c25918e5053f04e12b4e5f X-Virus-Checked: Checked by ClamAV on apache.org --001a11c25918e5053f04e12b4e5f Content-Type: text/plain; charset=ISO-8859-1 I copied the sstables and then ran a repair. It worked. Looks like export and import may have been much faster given that we had very little data. Thanks everyone. On Tue, Jul 9, 2013 at 1:34 PM, sankalp kohli wrote: > Hi Aaron, > Can he not specify all 256 tokens in the YAML of the new > cluster and then copy sstables? > I know it is a bit ugly but should work. > > Sankalp > > > On Tue, Jul 9, 2013 at 3:19 AM, Baskar Duraikannu < > baskar.duraikannu.db@gmail.com> wrote: > >> Thanks Aaron >> >> On 7/9/13, aaron morton wrote: >> >> Can I just copy data files for the required keyspaces, create schema >> >> manually and run repair? >> > If you have something like RF 3 and 3 nodes then yes, you can copy the >> data >> > from one node in the source cluster to all nodes in the dest cluster >> and use >> > cleanup to remove the unneeded data. Because each node in the source >> cluster >> > has a full copy of the data. >> > >> > If that's not the case you cannot copy the data files, even if they >> have the >> > same number of nodes, because the nodes in the dest cluster will have >> > different tokens. AFAIK you need to export the full data set from the >> source >> > DC and then import it into the dest system. >> > >> > The Bulk Load utility may be of help >> > http://www.datastax.com/docs/1.2/references/bulkloader . You could >> copy the >> > SSTables from every node in the source system and bulk load them into >> the >> > dest system. That process will ensure rows are sent to nodes that are >> > replicas. >> > >> > Cheers >> > >> > ----------------- >> > Aaron Morton >> > Freelance Cassandra Consultant >> > New Zealand >> > >> > @aaronmorton >> > http://www.thelastpickle.com >> > >> > On 9/07/2013, at 12:45 PM, Baskar Duraikannu >> > wrote: >> > >> >> We have two clusters used by two different groups with vnodes enabled. >> Now >> >> there is a need to move some of the keyspaces from cluster 1 to >> cluster 2. >> >> >> >> >> >> Can I just copy data files for the required keyspaces, create schema >> >> manually and run repair? >> >> >> >> Anything else required? Please help. >> >> -- >> >> Thanks, >> >> Baskar Duraikannu >> > >> > >> > > --001a11c25918e5053f04e12b4e5f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

I copied the sstables and then ran a = repair. It worked. Looks like export and import may have been much faster g= iven that we had very little data.

Thanks everyone= .



On Tue, Jul 9, 2013 at 1:34 PM, sankalp kohli = <kohlisankalp@gmail.com> wrote:
Hi Aaron,
=A0 =A0 =A0 = =A0 =A0 =A0 =A0Can he not specify all 256 tokens in the YAML of the new clu= ster and then copy sstables?=A0
I know it is a bit ugly but should work.
<= font color=3D"#888888">

Sankalp


On Tue, Jul 9, = 2013 at 3:19 AM, Baskar Duraikannu <baskar.duraikannu.db@gmai= l.com> wrote:
Thanks Aaron

On 7/9/13, aaron morton <aaron@thelastpickle.com> wrote:
>> Can I just copy data files for the required keyspaces, create sche= ma
>> manually and run repair?
> If you have something like RF 3 and 3 nodes then yes, you can copy the= data
> from one node in the source cluster to all nodes in the dest cluster a= nd use
> cleanup to remove the unneeded data. Because each node in the source c= luster
> has a full copy of the data.
>
> If that's not the case you cannot copy the data files, even if the= y have the
> same number of nodes, because the nodes in the dest cluster will have<= br> > different tokens. AFAIK you need to export the full data set from the = source
> DC and then import it into the dest system.
>
> The Bulk Load utility may be of help
> http://www.datastax.com/docs/1.2/references/bulkloader .= You could copy the
> SSTables from every node in the source system and bulk load them into = the
> dest system. That process will ensure rows are sent to nodes that are<= br> > replicas.
>
> Cheers
>
> -----------------
> Aaron Morton
> Freelance Cassandra Consultant
> New Zealand
>
> @aaronmorton
> http://www.= thelastpickle.com
>
> On 9/07/2013, at 12:45 PM, Baskar Duraikannu
> <baskar.duraikannu.db@gmail.com> wrote:
>
>> We have two clusters used by two different groups with vnodes enab= led. Now
>> there is a need to move some of the keyspaces from cluster 1 to cl= uster 2.
>>
>>
>> Can I just copy data files for the required keyspaces, create sche= ma
>> manually and run repair?
>>
>> Anything else required? =A0Please help.
>> --
>> Thanks,
>> Baskar Duraikannu
>
>


--001a11c25918e5053f04e12b4e5f--