cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joaquin Casares (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8338) Simplify Token Selection
Date Wed, 19 Nov 2014 22:15:34 GMT

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

Joaquin Casares commented on CASSANDRA-8338:
--------------------------------------------

Until DSE fully supports vnodes for all components I would hope so since we still have future
installs using non-vnode clusters/data centers.

> Simplify Token Selection
> ------------------------
>
>                 Key: CASSANDRA-8338
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8338
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Config
>            Reporter: Joaquin Casares
>            Priority: Trivial
>              Labels: lhf
>
> When creating provisioning scripts, especially when running tools like Chef, each node
is launched individually. When not using vnodes your initial setup will always be unbalanced
unless you handle token assignment within your scripts. 
> I spoke to someone recently who was using this in production and his operations team
wasn't too pleased that they had to use OpsCenter as an extra step for rebalancing. Instead,
we should provide this functionality out of the box for new clusters.
> Instead, could we have the following options below the initial_token section?
> {CODE}
> # datacenter_index: 0
> # node_index: 0
> # datacenter_size: 1
> {CODE}
> The above configuration options, when uncommented, would do the math of:
> {CODE}
> token = node_index * (range / datacenter_size) + (datacenter_index * 1000000) + start_of_range
> {CODE}
> This means that users don't have to repeatedly implement the initial_token selection
code nor know the range and offsets of their partitioner.



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

Mime
View raw message