You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Ahmed Eljami <ah...@gmail.com> on 2019/01/28 08:44:24 UTC
Question about allocate_tokens_for_keyspace
Hi Folks,
I'm about to configure a new cluster with num_token = 32 and using the new
token allocation.
For the first keyspace, I understood that it will be used to start my
cluster: allocate_tokens_for_keyspace = my_first_ks.
My question is how about the rest of keyspaces ? they will take the same
conf than the first ks or I have to add them to the cassandra.yaml and
restart each time my cluster?
Thanks
Fwd: Question about allocate_tokens_for_keyspace
Posted by onmstester onmstester <on...@zoho.com.INVALID>.
You could only have one keyspace for the value of allocate_tokens_for_keyspace to specify a keyspace from which the algorithm can find the replication to optimize for. So as far as your keyspaces are using similar replication strategies and replication factor you should not worry about this.
for more detail read this doc:
https://www.datastax.com/dev/blog/token-allocation-algorithm
Sent using https://www.zoho.com/mail/
============ Forwarded message ============
From : Ahmed Eljami <ah...@gmail.com>
To : <us...@cassandra.apache.org>
Date : Mon, 28 Jan 2019 12:14:24 +0330
Subject : Question about allocate_tokens_for_keyspace
============ Forwarded message ============
Hi Folks,
I'm about to configure a new cluster with num_token = 32 and using the new token allocation.
For the first keyspace, I understood that it will be used to start my cluster: allocate_tokens_for_keyspace = my_first_ks.
My question is how about the rest of keyspaces ? they will take the same conf than the first ks or I have to add them to the cassandra.yaml and restart each time my cluster?
Thanks
Re: Question about allocate_tokens_for_keyspace
Posted by Ahmed Eljami <ah...@gmail.com>.
Thanks Horia,
Yes we use Murmur3Partionner.
And yes we should have the same replication strategy for all KSs.
Le lun. 28 janv. 2019 à 10:44, Horia Mocioi <a....@gmail.com> a écrit :
> Hello,
>
> When configuring this option, the replication strategy of that keyspace
> will be used to optimize token selection, so this is useful when you have a
> single keyspace across the cluster or the same replication strategy for all
> keyspaces.
>
> Also, is worth noting that the option is available for Murmur3Partitioner.
>
> Regards,
> Horia
>
> On Mon, Jan 28, 2019 at 9:44 AM Ahmed Eljami <ah...@gmail.com>
> wrote:
>
>> Hi Folks,
>>
>> I'm about to configure a new cluster with num_token = 32 and using the
>> new token allocation.
>>
>> For the first keyspace, I understood that it will be used to start my
>> cluster: allocate_tokens_for_keyspace = my_first_ks.
>>
>> My question is how about the rest of keyspaces ? they will take the same
>> conf than the first ks or I have to add them to the cassandra.yaml and
>> restart each time my cluster?
>>
>> Thanks
>>
>>
>
> --
> <http://bookreader.ro>
>
--
Cordialement;
Ahmed ELJAMI
Re: Question about allocate_tokens_for_keyspace
Posted by Horia Mocioi <a....@gmail.com>.
Hello,
When configuring this option, the replication strategy of that keyspace
will be used to optimize token selection, so this is useful when you have a
single keyspace across the cluster or the same replication strategy for all
keyspaces.
Also, is worth noting that the option is available for Murmur3Partitioner.
Regards,
Horia
On Mon, Jan 28, 2019 at 9:44 AM Ahmed Eljami <ah...@gmail.com> wrote:
> Hi Folks,
>
> I'm about to configure a new cluster with num_token = 32 and using the new
> token allocation.
>
> For the first keyspace, I understood that it will be used to start my
> cluster: allocate_tokens_for_keyspace = my_first_ks.
>
> My question is how about the rest of keyspaces ? they will take the same
> conf than the first ks or I have to add them to the cassandra.yaml and
> restart each time my cluster?
>
> Thanks
>
>
--
<http://bookreader.ro>