incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremiah D Jordan <jeremiah.jor...@gmail.com>
Subject Re: Node tokens / data move
Date Sat, 13 Jul 2013 19:53:39 GMT
Pretty sure you can put the list in the yaml file too.

-Jeremiah

On Jul 12, 2013, at 3:09 AM, aaron morton <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
> 
> -----------------
> Aaron Morton
> Cassandra Consultant
> New Zealand
> 
> @aaronmorton
> 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
>> >
>> >
>> 
>> 
> 


Mime
View raw message