[
https://issues.apache.org/jira/browse/CASSANDRA-16205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17218065#comment-17218065
]
Paulo Motta commented on CASSANDRA-16205:
-----------------------------------------
We used to have a single token generator tool from CASSANDRA-3709 but it was
removed on CASSANDRA-5261.
I'm trying to think from the user's point of view what's the benefit of using
the {{allocate_tokens_for_local_replication_factor}} algorithm to generate
tokens for a new cluster versus manually generating tokens by splitting the
ring into #nodes/#vnodes segments and assign each segment in a round-robin
fashion to each node, since the latter option will always generate a more
balanced allocation?
I did a quick test with 4 nodes, 4 tokens per node, RF=2 and the generated
ownership was:
* with 2 racks: 27%, 27%, 23%, 23%
* without racks: 22%, 26%, 24%, 28%
If the objective here is to pre-generate tokens to speed up dtests on
CASSANDRA-16079, couldn't we generate them using the latter approach on
ccm/dtest ?
> Offline token allocation strategy generator tool
> ------------------------------------------------
>
> Key: CASSANDRA-16205
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16205
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Config, Local/Scripts
> Reporter: Michael Semb Wever
> Assignee: Michael Semb Wever
> Priority: Normal
>
> A command line tool to generate tokens (using the
> allocate_tokens_for_local_replication_factor algorithm) for pre-configuration
> of {{initial_tokens}} in cassandra.yaml.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
