Re: Node tokens / data move

> > if you've got a non-vnode cluster and are trying to convert, you are > likely going to at least want, if not have to, run shuffle Fair enough. Running shuffle after upgrading to using vnodes is nearly mandatory or else you'll run into troubles when adding more nodes (see this Jira ticket

Re: Node tokens / data move

Eric, Unfortunately if you've got a non-vnode cluster and are trying to convert, you are likely going to at least want, if not have to, run shuffle. It isn't a pleasant situation when you run into that because in order for the shuffle to execute safely and successfully you need to have essentiall

Re: Node tokens / data move

> > vnodes currently do not brings any noticeable benefits to outweight trouble The main advantage of vnodes is that it lets you have flexibility with respect to adding and removing nodes from your cluster without having to rebalance your cluster (issuing a lot of moves). A shuffle is a lot of m

Re: Node tokens / data move

My understanding is that it is not possible to change the number of tokens after the node has been initialized. that was my conclusion too. vnodes currently do not brings any noticeable benefits to outweight trouble. shuffle is very slow in large cluster. Recovery is faster with vnodes but i h

Re: Node tokens / data move

> Pretty sure you can put the list in the yaml file too. Yup, sorry. initial_tokens can take a comma separated value Cheers - Aaron Morton Cassandra Consultant New Zealand @aaronmorton http://www.thelastpickle.com On 15/07/2013, at 9:44 AM, Eric Stevens wrote: > My understand

Re: Node tokens / data move

My understanding is that it is not possible to change the number of tokens after the node has been initialized. To do so you would first need to decommission the node, then start it clean with the appropriate num_tokens in the yaml. On Fri, Jul 12, 2013 at 9:17 PM, Radim Kolar wrote: > its pos

Re: Node tokens / data move

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? >> I know it is a bit ugly but should work. > You can pass a comma sepa

Re: Node tokens / data move

its possible to change num_tokens on node with data? i changed it and restarted node but it still has same amount in nodetool status.

Re: Node tokens / data move

> 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

Re: Node tokens / data move

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

Re: Node tokens / data move

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...@gmail.com> wrote: > Thanks Aaron > > On 7/9/13, aaron morton

Re: Node tokens / data move

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

Re: Node tokens / data move

> 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