cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13664) RangeFetchMapCalculator should not try to optimise 'trivial' ranges
Date Thu, 06 Jul 2017 16:44:00 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16076867#comment-16076867
] 

Ariel Weisberg commented on CASSANDRA-13664:
--------------------------------------------

Changes makes sense to me. Can you run the dtests just to sanity check?

> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message