[
https://issues.apache.org/jira/browse/CASSANDRA-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-1037.
---------------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 0.8)
node-at-a-time loadbalance feels like a dead end.
> Improve load balancing to take into account load in terms of operations
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-1037
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1037
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jeremy Hanna
> Priority: Minor
>
> Currently in cassandra, the load balancing takes into account disk space.
> When using an order-preserving partitioner, there can be hot spots in the
> various ranges of tokens in terms of operations. We would like to propose
> improving the load balancing so that it takes that the number of operations
> into account.
> There are two places where this can be handled:
> 1. when the cluster decides on which nodes need to be balanced out.
> 2. how to balance an individual node - where to split
> For number 1, the number of operations that a node performed could be
> factored in to how important it is to balance that node.
> For number 2, we are already using a midpoint in the node when trying to load
> balance with respect to space. We would propose adding a weight to the
> midpoint to lean towards splitting so that the operational load could be
> better handled, not just space.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
