cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-13664) RangeFetchMapCalculator should not try to optimise 'trivial' ranges
Date Mon, 14 Aug 2017 12:36:00 GMT


Marcus Eriksson updated CASSANDRA-13664:
       Resolution: Fixed
    Fix Version/s:     (was: 4.x)
           Status: Resolved  (was: Ready to Commit)


> RangeFetchMapCalculator should not try to optimise 'trivial' ranges
> -------------------------------------------------------------------
>                 Key: CASSANDRA-13664
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>             Fix For: 4.0
>         Attachments: Screen Shot 2017-08-14 at 14.22.23.png
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message