Hi Jean,
Good question. I think that sentence is slightly confusing and here is why:
If the cluster has tokens are already evenly distributed and there is no
plans to expand the cluster, then applying the allocate_tokens_for_keyspace
setting has no real practical value.
If the cluster has tokens
Hello Anthony,
Effectively I did not start the seed of every rack firsts. Thank you for
the post. I believe this is something important to have as official
documentation in cassandra.apache.org. This issues as many others are not
documented properly.
Of course I find the blog of last pickle very
Hi Jean,
It sounds like there are no nodes in one of the racks for the eu-west-3
datacenter. What does the output of nodetool status look like currently?
Note, you will need to start a node in each rack before creating the
keyspace. I wrote a blog post with the procedure to set up a new cluster
u
Creating a fresh new cluster in aws using this procedure, I got this
problem once I am bootstrapping the second rack of the cluster of 6
machines with 3 racks and a keyspace of rf 3
WARN [main] 2019-04-26 11:37:43,845 TokenAllocation.java:63 - Selected
tokens [-5106267594614944625, 62300144644971
Hi folks,
What about adding new keyspaces in the existing cluster, test_2 with the
same RF.
It will use the same logic as the existing kesypace test ? Or I should
restart nodes and add the new keyspace to the cassandra.yaml ?
Thanks.
Le mar. 2 oct. 2018 à 10:28, Varun Barala a
écrit :
> Hi,
>
Hi,
Managing `initial_token` by yourself will give you more control over
scale-in and scale-out.
Let's say you have three node cluster with `num_token: 1`
And your initial range looks like:-
Datacenter: datacenter1
==
AddressRackStatus State LoadOwns
Token
Sent using Zoho Mail On Mon, 01 Oct 2018 18:36:03 +0330 Alain RODRIGUEZ
wrote Hello again :), I thought a little bit more
about this question, and I was actually wondering if something like this would
work: Imagine 3 node cluster, and create them using: For the 3 nodes:
`num_token: 4
e operational complexity is
reduced by automated operations and/or having a good tooling to operate
efficiently.
Le lun. 1 oct. 2018 à 12:37, onmstester onmstester a
écrit :
> Thanks Alex,
> You are right, that would be a mistake.
>
> Sent using Zoho Mail <https://www.zoho.co
Thanks Alex, You are right, that would be a mistake. Sent using Zoho Mail
Forwarded message From : Oleksandr Shulgin
To : "User" Date :
Mon, 01 Oct 2018 13:53:37 +0330 Subject : Re: Re: how to configure the Token
Allocation Algorithm Forward
On Mon, Oct 1, 2018 at 12:18 PM onmstester onmstester
wrote:
>
> What if instead of running that python and having one node with non-vnode
> config, i remove the first seed node and re-add it after cluster was fully
> up ? so the token ranges of first seed node would also be assigned by
> Allocat
From : Alain
RODRIGUEZ To : "user
cassandra.apache.org" Date : Mon, 01 Oct 2018
13:14:21 +0330 Subject : Re: how to configure the Token Allocation Algorithm
Forwarded message Hello, Your process looks good to
me :). Still a couple of comments to make it more
Hello,
Your process looks good to me :). Still a couple of comments to make it
more efficient (hopefully).
*- Improving step 2:*
I believe you can actually get a slightly better distribution picking the
tokens for the (first) seed node. This is to prevent the node from randomly
calculating its t
Since i failed to find a document on how to configure and use the Token
Allocation Algorithm (to replace the random Algorithm), just wanted to be sure
about the procedure i've done: 1. Using Apache Cassandra 3.11.2 2. Configured
one of seed nodes with num_tokens=8 and started it. 3. Using Cqlsh
13 matches
Mail list logo
