cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4443) shuffle utility for vnodes
Date Thu, 26 Jul 2012 22:48:34 GMT


Eric Evans commented on CASSANDRA-4443:

bq. Eric has some notes up at on implementation
but a wiki is a lousy discussion medium so I'll post here:

It is, but so is Jira. :)

I'm not trying to start a discussion on the wiki, I just wanted to get down the general requirements
and brain-storm a bit so that any subsequent discussion (if needed) might be more productive.

bq. shuffle should operate on the entire cluster, at least by default. 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.

Yeah, this is exactly the sort of thing I was trying to capture (and I've added it).
> shuffle utility for vnodes
> --------------------------
>                 Key: CASSANDRA-4443
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core
>    Affects Versions: 1.2
>            Reporter: Brandon Williams
>            Assignee: Eric Evans
>             Fix For: 1.2
> As mentioned on CASSANDRA-4127, for upgrades we need a 'shuffle' command to split up
the contiguous ranges.  

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message