[
https://issues.apache.org/jira/browse/CASSANDRA-13701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16552732#comment-16552732
]
Kurt Greaves commented on CASSANDRA-13701:
------------------------------------------
Possibly, but it's doubling up on meanings for a single property. I can see a
case where your default is not necessarily the same RF as your biggest keyspace
(which is what you want to set the allocation algorithm to), and it's not
exactly clear how it would work with multi-dc and different RF's per DC. I
think Datastax did it right by moving to specifying the RF including multi-dc
in the yaml.
> Lower default num_tokens
> ------------------------
>
> Key: CASSANDRA-13701
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13701
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Chris Lohfink
> Priority: Minor
>
> For reasons highlighted in CASSANDRA-7032, the high number of vnodes is not
> necessary. It is very expensive for operations processes and scanning. Its
> come up a lot and its pretty standard and known now to always reduce the
> num_tokens within the community. We should just lower the defaults.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
