You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by Apache Wiki <wi...@apache.org> on 2012/08/02 20:19:03 UTC
[Cassandra Wiki] Update of "VirtualNodes/Balance" by EricEvans
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.
The "VirtualNodes/Balance" page has been changed by EricEvans:
http://wiki.apache.org/cassandra/VirtualNodes/Balance?action=diff&rev1=5&rev2=6
Comment:
shuffles as long running tasks
* "Shuffling node at a time means that for each node i for i in 0..N-1 (where N is the cluster size), i/N of the ranges shuffled will, on average, have been shuffled at least once already. So it's substantially less efficient than shuffling once, then assigning the vnodes out in one cluster-wide pass." -- ''Jonathan Ellis''<<FootNote([[https://issues.apache.org/jira/browse/CASSANDRA-4443?focusedCommentId=13423505&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13423505|CASSANDRA-4443#comment-13423505]])>>
+ * Shuffling will entail moving a ''lot'' of data around the cluster and so has the potential to consume a lot of disk and network I/O, and to take a considerable amount of time. For this to be an online operation, the shuffle will need to operate on a lower priority basis to other streaming operations, and should be expected to take days or weeks to complete.
+
=== Nodes / Cluster ===
The most straightforward method of effecting ownership is a token move (i.e. relocating a range from one node to another). Exposing this with JMX would allow implementing all of the required operations client-side.