[
https://issues.apache.org/jira/browse/CASSANDRA-13701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155036#comment-17155036
]
Jeremy Hanna commented on CASSANDRA-13701:
------------------------------------------
So if it's a matter of like Dimitar says, making the bootstraps sequential,
then that isn't strictly an error as much as an unfortunate side effect of the
new algorithm with dtest parallelism. So there appears to be two paths forward:
1) Use the randomized algorithm both in tests and in the defaults with a higher
num_tokens count
2) Change the dtests with bootstrapping/joining to be sequential with the new
defaults
Is it possible to start by trying option 2 and see where that gets us in terms
of dtest runtimes and errors? I don't want to go down a rabbit hole but it
would be nice to quantify the trade-offs.
> Lower default num_tokens
> ------------------------
>
> Key: CASSANDRA-13701
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13701
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Config
> Reporter: Chris Lohfink
> Assignee: Jeremy Hanna
> Priority: Low
>
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
