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 <ahmed.elj...@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>
