[
https://issues.apache.org/jira/browse/CASSANDRA-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-13664:
----------------------------------------
Status: Patch Available (was: Open)
https://github.com/krummas/cassandra/commits/marcuse/opt_large
simply filters out ranges considered trivial (less than 1000 tokens for RP and
M3P, no trivial ranges for BOP etc), then re-adds them once the optimisation is
done.
> RangeFetchMapCalculator should not try to optimise 'trivial' ranges
> -------------------------------------------------------------------
>
> Key: CASSANDRA-13664
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13664
> Project: Cassandra
> Issue Type: Bug
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Fix For: 4.x
>
>
> RangeFetchMapCalculator (CASSANDRA-4650) tries to make the number of streams
> out of each node as even as possible.
> In a typical multi-dc ring the nodes in the dcs are setup using token + 1,
> creating many tiny ranges. If we only try to optimise over the number of
> streams, it is likely that the amount of data streamed out of each node is
> unbalanced.
> We should ignore those trivial ranges and only optimise the big ones, then
> share the tiny ones over the nodes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
