[
https://issues.apache.org/jira/browse/CASSANDRA-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12867241#action_12867241
]
Suhail Doshi commented on CASSANDRA-1086:
-----------------------------------------
We've had very few problems. Placing the calculated token as the InitialToken
with autobootstrap on usually went flawlessly.
The only issue I've ever seen is restarting a node it was grabbing data from; a
quick fix was just restarting the node that is bootstrapping to restart the
process. We just feel we can predict what's going to happen in production a lot
better then it choosing something by itself.
> Token range calculator
> ----------------------
>
> Key: CASSANDRA-1086
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1086
> Project: Cassandra
> Issue Type: Improvement
> Components: Contrib
> Affects Versions: 0.6.1
> Reporter: Suhail Doshi
> Priority: Trivial
>
> We found loadbalance and autobootstrapping to be sub-par in production; also
> very risky too if it guesses anything wrong.
> We created a simple Python script that I am sure can be greatly improved to
> be more automated but thought we'd throw it up here anyway:
> http://gist.github.com/399336
> In a nutshell: give it your current token ranges, the load for that range,
> and it'll suggest you the best token to help load balance your cluster when
> you decide to add a new node. We've used it countless times in production
> ourselves. Our way of contributing some small back to the community.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
