On Thu, Feb 14, 2013 at 5:48 PM, Daning Wang wrote:
> Thanks! suppose I can upgrade to 1.2.x with 1 token by commenting out
> num_tokens, how can I changed to multiple tokens? could not find doc clearly
> stating about this.
If you decided to move to virtual nodes after upgrading to 1.2, you
can
There was a webinar (Datastax C*llege) about Vnodes. It will be available
soon there I guess: http://www.datastax.com/resources/webinars/collegecredit.
You could have watch it live and ask your own questions.
Here is a howto:
http://www.datastax.com/dev/blog/upgrading-an-existing-cluster-to-vnodes
Thanks! suppose I can upgrade to 1.2.x with 1 token by commenting out
num_tokens, how can I changed to multiple tokens? could not find doc
clearly stating about this.
On Thu, Feb 14, 2013 at 10:54 AM, Alain RODRIGUEZ wrote:
> From:
> http://www.datastax.com/docs/1.2/configuration/node_configura
From:
http://www.datastax.com/docs/1.2/configuration/node_configuration#num-tokens
About num_tokens: "If left unspecified, Cassandra uses the default value of
1 token (for legacy compatibility) and uses the initial_token. If you
already have a cluster with one token per node, and wish to migrate t
Thanks Aaron and Manu.
Since we are using 1.1, there is no num_taken parameter. when I upgrade to
1.2, should I set num_token=1 to start up, or I can set to other numbers?
Daning
On Tue, Feb 12, 2013 at 3:45 PM, Manu Zhang wrote:
> num_tokens is only used at bootstrap
>
> I think it's also
>
> num_tokens is only used at bootstrap
I think it's also used in this case (already bootstrapped with num_tokens =
1 and now num_tokens > 1). Cassandra will split a node's current range into
*num_tokens* parts and there should be no change to the amount of ring a
node holds before shuffling.
O
Restore the settings for num_tokens and intial_token to what they were before
you upgraded.
They should not be changed just because you are upgrading to 1.2, they are used
to enable virtual nodes. Which are not necessary to run 1.2.
Cheers
-
Aaron Morton
Freelance Cassandra D
No, I did not run shuffle since the upgrade was not successful.
what do you mean "reverting the changes to num_tokens and inital_token"?
set num_tokens=1? initial_token should be ignored since it is not
bootstrap. right?
Thanks,
Daning
On Tue, Feb 12, 2013 at 10:52 AM, aaron morton wrote:
> We
Were you upgrading to 1.2 AND running the shuffle or just upgrading to 1.2?
If you have not run shuffle I would suggest reverting the changes to num_tokens
and inital_token. This is a guess because num_tokens is only used at bootstrap.
Just get upgraded to 1.2 first, then do the shuffle when t
Thanks Aaron.
I tried to migrate existing cluster(ver 1.1.0) to 1.2.1 but failed.
- I followed http://www.datastax.com/docs/1.2/install/upgrading, have
merged cassandra.yaml, with follow parameter
num_tokens: 256
#initial_token: 0
the initial_token is commented out, current token should be obta
There is a command line utility in 1.2 to shuffle the tokens…
http://www.datastax.com/dev/blog/upgrading-an-existing-cluster-to-vnodes
$ ./cassandra-shuffle --help
Missing sub-command argument.
Usage: shuffle [options]
Sub-commands:
create Initialize a new shuffle operation
ls
On Sun 03 Feb 2013 05:45:56 AM CST, Daning Wang wrote:
I'd like to upgrade from 1.1.6 to 1.2.1, one big feature in 1.2 is
that it can have multiple tokens in one node. but there is only one
token in 1.1.6.
how can I upgrade to 1.2.1 then breaking the token to take advantage
of this feature? I we
I'd like to upgrade from 1.1.6 to 1.2.1, one big feature in 1.2 is that it
can have multiple tokens in one node. but there is only one token in 1.1.6.
how can I upgrade to 1.2.1 then breaking the token to take advantage of
this feature? I went through this doc but it does not say how to change the
13 matches
Mail list logo
