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 88819109A4 for ; Sat, 13 Jul 2013 19:54:11 +0000 (UTC) Received: (qmail 72858 invoked by uid 500); 13 Jul 2013 19:54:08 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 72836 invoked by uid 500); 13 Jul 2013 19:54:08 -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 72828 invoked by uid 99); 13 Jul 2013 19:54:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Jul 2013 19:54:08 +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 (nike.apache.org: domain of jeremiah.jordan@gmail.com designates 209.85.223.181 as permitted sender) Received: from [209.85.223.181] (HELO mail-ie0-f181.google.com) (209.85.223.181) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Jul 2013 19:54:02 +0000 Received: by mail-ie0-f181.google.com with SMTP id x12so22787669ief.40 for ; Sat, 13 Jul 2013 12:53:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:message-id:mime-version:subject:date:references :to:in-reply-to:x-mailer; bh=9nzDhCh3i/U+RNVVQAtvej2vzYrwXC07/nCnFPC/irc=; b=zWSTrBq5awLSb9ixNakrB5d45juXRL8yepsjbNtdgeyKVXL98TpEum8G58RoaciZFG 1dSZ1I1fUwXlSzyF51hQeq08q3YGWXwxR8MiHXDhpyKxTGWCA9ibAkBDTvQH8QmmKKiI Uv/MAoA1MAFG5mVcv/g0zpigkOqkOecNSM9gg+Xl37hgg75WEdxG650OKAAEHWBuL3oy 9fl+5epg7tgXGlNmd0pvvGI3B3BUBB+pMkGiolt1aamWYwM0g9p1KR9NR0tYmXbMBtwI YajC1Ak6S2A2i98zkVBgUvO2w6OP/Yk1YncOUvAC7t4/2aZsZsTXZIwUrhrK4Toa1Fvb 86qA== X-Received: by 10.43.12.198 with SMTP id pj6mr15007315icb.68.1373745221140; Sat, 13 Jul 2013 12:53:41 -0700 (PDT) Received: from [192.168.2.10] (c-71-201-190-179.hsd1.il.comcast.net. [71.201.190.179]) by mx.google.com with ESMTPSA id p10sm7406998igx.4.2013.07.13.12.53.40 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 13 Jul 2013 12:53:40 -0700 (PDT) From: Jeremiah D Jordan Content-Type: multipart/alternative; boundary="Apple-Mail=_09AF1999-3A04-437F-B8FE-460030DF63BA" Message-Id: <6C55FFF2-78A8-47E0-A97E-89197A20876D@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: Node tokens / data move Date: Sat, 13 Jul 2013 14:53:39 -0500 References: To: user@cassandra.apache.org In-Reply-To: X-Mailer: Apple Mail (2.1508) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_09AF1999-3A04-437F-B8FE-460030DF63BA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Pretty sure you can put the list in the yaml file too. -Jeremiah On Jul 12, 2013, at 3:09 AM, aaron morton = wrote: >> Can he not specify all 256 tokens in the YAML of the new = cluster and then copy sstables?=20 >> I know it is a bit ugly but should work. > You can pass a comma separated list of tokens to the = -Dcassandra.replace_token JVM param.=20 >=20 > AFAIK it's not possible to provide the list in the yaml file.=20 >=20 > Cheers > A >=20 > ----------------- > Aaron Morton > Cassandra Consultant > New Zealand >=20 > @aaronmorton > http://www.thelastpickle.com >=20 > On 11/07/2013, at 5:07 AM, Baskar Duraikannu = wrote: >=20 >>=20 >> 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. >>=20 >> Thanks everyone. >>=20 >>=20 >>=20 >>=20 >> 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?=20 >> I know it is a bit ugly but should work. >>=20 >> Sankalp >>=20 >>=20 >> On Tue, Jul 9, 2013 at 3:19 AM, Baskar Duraikannu = wrote: >> Thanks Aaron >>=20 >> 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 >> > >> > >>=20 >>=20 >=20 --Apple-Mail=_09AF1999-3A04-437F-B8FE-460030DF63BA Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 aaron@thelastpickle.com> = wrote:
      =        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.
You can pass a = comma separated list of tokens to the -Dcassandra.replace_token JVM = param. 

AFAIK it's not possible to provide the = list in the yaml = file. 

Cheers
A

http://www.thelastpickle.com

On 11/07/2013, at 5:07 AM, Baskar Duraikannu <baskar.duraikannu.db@gmail.= com> wrote:


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 <kohlisankalp@gmail.com> 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 <aaron@thelastpickle.com> 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
> <baskar.duraikannu.db@gmail.com> 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
>
>


=


= --Apple-Mail=_09AF1999-3A04-437F-B8FE-460030DF63BA--