cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dikang Gu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12777) Optimize the vnode allocation for single replica per DC
Date Thu, 20 Oct 2016 15:59:59 GMT

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

Dikang Gu commented on CASSANDRA-12777:
---------------------------------------

Cool, revert the change to the test, and rebase on trunk, https://github.com/DikangGu/cassandra/commit/fbadd16cf9fb144445db2d8afeb261a67313fd25

Thanks!

> Optimize the vnode allocation for single replica per DC
> -------------------------------------------------------
>
>                 Key: CASSANDRA-12777
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12777
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Dikang Gu
>            Assignee: Dikang Gu
>             Fix For: 3.x
>
>
> The new vnode allocation algorithm introduced in CASSANDRA-7032 is optimized for the
situation that there are multiple replicas per DC.
> In our production environment, most cluster only has one replica, in this case, the algorithm
does not work perfectly. It always tries to split token ranges by half, so that the ownership
of "min" node could go as low as ~60% compared to avg.
> So for single replica case, I'm working on a new algorithm, which is based on Branimir's
previous commit, to split token ranges by "some" percentage, instead of always by half. In
this way, we can get a very small variation of the ownership among different nodes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message