Re: Removing initial_token parameter

2018-03-09 Thread kurt greaves
correct, tokens will be stored in the nodes system tables after the first boot, so feel free to remove them (although it's not really necessary) On 9 Mar. 2018 20:16, "Mikhail Tsaplin" wrote: > Is it safe to remove initial_token parameter on a cluster created by > snaps

Removing initial_token parameter

2018-03-09 Thread Mikhail Tsaplin
Is it safe to remove initial_token parameter on a cluster created by snapshot restore procedure presented here https://docs.datastax.com /en/cassandra/latest/cassandra/operations/opsSnapshotRestoreNewCluster.html ? For me, it seems that initial_token parameter is used only when nodes are started

Re: Joining a cluster of nodes having multi valued initial_token parameters.

2018-03-09 Thread Mikhail Tsaplin
I suspect that cluster was created by recovering from a snapshot. PS. I asked a related question on this mailing list. Please check subject: Removing initial_token parameter. 2018-03-08 20:02 GMT+07:00 Oleksandr Shulgin : > On Thu, Mar 8, 2018 at 1:41 PM, Mikhail Tsaplin > wrote: >

Re: Joining a cluster of nodes having multi valued initial_token parameters.

2018-03-08 Thread Oleksandr Shulgin
On Thu, Mar 8, 2018 at 1:41 PM, Mikhail Tsaplin wrote: > Thank you for the answer, are you sure that it at least safe? > I would test in a lab first of course, but I don't see why it should be a problem. I wonder more why did you have tokens listed explicitly on the existing nodes if they are r

Re: Joining a cluster of nodes having multi valued initial_token parameters.

2018-03-08 Thread Mikhail Tsaplin
de Cassandra cluster. Every node has initial_token >> configuration parameter holding 256 tokens (looks like randomly >> distributed). Now I have to add a fourth node. How could this be done? >> > > I think the easiest and safest way would be to use num_tokens=256 and not >

Re: Joining a cluster of nodes having multi valued initial_token parameters.

2018-03-08 Thread Oleksandr Shulgin
On Thu, Mar 8, 2018 at 12:09 PM, Mikhail Tsaplin wrote: > Hi, > > I have a three node Cassandra cluster. Every node has initial_token > configuration parameter holding 256 tokens (looks like randomly > distributed). Now I have to add a fourth node. How could this be done? > I

Joining a cluster of nodes having multi valued initial_token parameters.

2018-03-08 Thread Mikhail Tsaplin
Hi, I have a three node Cassandra cluster. Every node has initial_token configuration parameter holding 256 tokens (looks like randomly distributed). Now I have to add a fourth node. How could this be done? PS. Part of 'nodetool ring' output: 192.168.1.123 rack1 Up No

Re: Rapid scaleup of cassandra nodes with snapshots and initial_token in the yaml

2018-02-20 Thread Carl Mueller
Ok, so vnodes are random assignments under normal circumstances (I'm in 2.1.x, I'm assuming a derivative approach was in the works that would avoid some hot node aspects of random primary range assingment for new nodes once you had one or two or three in a cluster). So... couldn't I just "engineer

Re: Rapid scaleup of cassandra nodes with snapshots and initial_token in the yaml

2018-02-16 Thread Carl Mueller
Thanks. Yeah, it appears this would only be doable if we didn't have vnodes and used old single token clusters. I guess Priam has something where you increase the cluster by whole number multiples. Then there's the issue of doing quorum read/writes if there suddenly is a new replica range with grey

Re: Rapid scaleup of cassandra nodes with snapshots and initial_token in the yaml

2018-02-15 Thread kurt greaves
Ben did a talk that might have some useful information. It's much more complicated with vnodes though and I doubt you'll be able to get it to be as rapid as you'd want. sets up schema to match This shou

Re: Rapid scaleup of cassandra nodes with snapshots and initial_token in the yaml

2018-02-15 Thread Jeff Jirsa
Short answer is "yes, with caveats". I recall a talk about this from Cassandra Summit ~2014 or so. I THINK it was from Instaclustr, but I'm not positive. Maybe Ben or Kurt or someone over there has more info (if it really was them)? On Wed, Feb 14, 2018 at 9:40 AM, Carl Mueller wrote: > http

Re: Rapid scaleup of cassandra nodes with snapshots and initial_token in the yaml

2018-02-15 Thread Carl Mueller
Or could we do a rapid clone to a new cluster, then add that as another datacenter? On Wed, Feb 14, 2018 at 11:40 AM, Carl Mueller wrote: > https://stackoverflow.com/questions/48776589/cassandra- > cant-one-use-snapshots-to-rapidly-scale-out-a-cluster/48778179#48778179 > > So the basic question

Rapid scaleup of cassandra nodes with snapshots and initial_token in the yaml

2018-02-14 Thread Carl Mueller
https://stackoverflow.com/questions/48776589/cassandra-cant-one-use-snapshots-to-rapidly-scale-out-a-cluster/48778179#48778179 So the basic question is, if one records tokens and snapshots from an existing node, via: nodetool ring | grep ip_address_of_node | awk '{print $NF ","}' | xargs for th

Re: initial_token

2013-02-02 Thread aaron morton
> > On Fri, Feb 1, 2013 at 12:55 PM, Víctor Hugo Oliveira Molinar > wrote: >> Do not set initial_token when using murmur3partitioner. >> instead, set num_tokens. >> >> For example, u have 3 hosts with the same hardware setup, then, for each one >> set the

Re: initial_token

2013-02-01 Thread Edward Capriolo
You do not just want to vnodes without being sure. Some queries are not optimized for vnodes and issue 128 slices to solve some secondaryIndexQueries. On Fri, Feb 1, 2013 at 12:55 PM, Víctor Hugo Oliveira Molinar wrote: > Do not set initial_token when using murmur3partitioner. > instea

Re: initial_token

2013-02-01 Thread Víctor Hugo Oliveira Molinar
Do not set initial_token when using murmur3partitioner. instead, set num_tokens. For example, u have 3 hosts with the same hardware setup, then, for each one set the same num_tokens. But now consider adding another better host, this time i'd suggest you to set previous num_tokens * 2. num_t

Re: initial_token

2013-01-31 Thread Edward Capriolo
This is the bad side of changing default. There are going to be a few groups unfortunates. The first group, who only can not setup their cluster, and eventually figure out their tokens. (this thread) The second group, who assume their tokens were correct and run around with an unbalanced cluster t

Re: initial_token

2013-01-31 Thread Rob Coli
On Thu, Jan 31, 2013 at 12:17 PM, Edward Capriolo wrote: > Now by default a new partitioner is chosen Murmer3. "Now" = as of 1.2, to be unambiguous. =Rob -- =Robert Coli AIM>ALK - rc...@palominodb.com YAHOO - rcoli.palominob SKYPE - rcoli_palominodb

Re: initial_token

2013-01-31 Thread Edward Capriolo
andraDaemon.java:397) > > at > org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:440) > > For input string: "85070591730234615865843651857942052864" > > Fatal configuration error; unable to start server. See log for stacktrace. > > > > From m

initial_token

2013-01-31 Thread Stephen.M.Thompson
65843651857942052864" Fatal configuration error; unable to start server. See log for stacktrace. >From my cassandra.yaml ... initial_token: 85070591730234615865843651857942052864 >From the wiki this certainly looks correct: http://www.datastax.com/docs/1.1/initialize/cluster_init I

Re: initial_token configuration

2013-01-09 Thread Manu Zhang
luster, it will pick >> # a random token, which will lead to hot spots. >> initial_token: > > > Hi all. I have questions about this comment. > > Will *Cassandra 1.2* request a token bisecting the range of the > heaviest-loaded existing node? (I don't find it in

Re: Re: can one keyspace has two groups of "initial_token"?

2011-12-18 Thread Edward Capriolo
amily one? > > > At 2011-12-18 01:44:23,"Edward Capriolo" wrote: > > No. Token and partitioner are cluster wide settings. You have to run > multiple instances of Cassandra. > > 2011/12/17 魏金仙 > >> My question is whether two groups of "initial_token

Re:Re: can one keyspace has two groups of "initial_token"?

2011-12-18 Thread 魏金仙
Cassandra. 2011/12/17 魏金仙 My question is whether two groups of "initial_token" can coexist since our goal is to partition data of each column family uniformly on 5 nodes. I deployed Cassandra 0.7.4 on a cluster of 5 nodes, using orderPreservingPartitioner. Two column families n

Re: can one keyspace has two groups of "initial_token"?

2011-12-17 Thread Edward Capriolo
No. Token and partitioner are cluster wide settings. You have to run multiple instances of Cassandra. 2011/12/17 魏金仙 > My question is whether two groups of "initial_token" can coexist since our > goal is to partition data of each column family uniformly on 5 nodes. > >

can one keyspace has two groups of "initial_token"?

2011-12-17 Thread 魏金仙
My question is whether two groups of "initial_token" can coexist since our goal is to partition data of each column family uniformly on 5 nodes. I deployed Cassandra 0.7.4 on a cluster of 5 nodes, using orderPreservingPartitioner. Two column families named CF1 and CF2 are creat

Re: Can initial_token be decimal or hexadecimal format?

2011-09-13 Thread Jonathan Ellis
Parsing is done by TokenFactory.fromString, so yes, it matters per partitioner. On Tue, Sep 13, 2011 at 4:09 AM, Mck wrote: > And does it matter when using different partitoners? > > In the config it seems only strings are used. > In RP it parses this string into a BigInteger so it needs to be in

Can initial_token be decimal or hexadecimal format?

2011-09-13 Thread Mck
And does it matter when using different partitoners? In the config it seems only strings are used. In RP it parses this string into a BigInteger so it needs to be in decimal format, but for ByteOrderPartitioner it uses FBUtilities.hexToBytes(..) when translating a string to a token (BytesToken).

Re: calculating initial_token

2011-03-14 Thread aaron morton
Once the node has started once, it will not use the value for initial_token in cassandra.yaml. Use nodetool move to assign a new token to the node. nodetool loadbalance is generally a bad idea www.spidertracks.com Aaron On 15 Mar 2011, at 13:04, Narendra Sharma wrote: > The %age (owns)

Re: calculating initial_token

2011-03-14 Thread Narendra Sharma
The %age (owns) is just the arc length in terms of %age of tokens a node owns out of the total token space. It doesn't reflect the actual data. The size (load) is the real current load. -Naren On Mon, Mar 14, 2011 at 2:59 PM, Sasha Dolgy wrote: > ah, you know ... i have been reading it wrong.

Re: calculating initial_token

2011-03-14 Thread Sasha Dolgy
ah, you know ... i have been reading it wrong. the output shows a nice fancy column called "Owns" but i've only ever seen the percentage ... the amount of data or "load" is even ... doh. thanks for the reply. cheers -sd On Mon, Mar 14, 2011 at 10:47 PM, Narendra Sharma wrote: > On the same pag

Re: calculating initial_token

2011-03-14 Thread Narendra Sharma
On the same page there is a section on Load Balance that talks about python script to compute tokens. I believe your question is more about assigning new tokens and not compute tokens. 1. "nodetool loadbalance" will result in recomputation of tokens. It will pick tokens based on the load and not t

calculating initial_token

2011-03-14 Thread Sasha Dolgy
Sorry for being a bit daft ... Wanted a bit of validation or rejection ... If I have a 6 node cluster, replication factor 2 (don't think this is applicable to the token decision) is the following sufficient and correct for determining the tokens: #!/bin/bash for nodes in {0..5}; do echo "$nod