On Mon, Aug 27, 2012 at 3:54 PM, Eric Evans wrote:
> Any thoughts on this? Should this be something baked into nodetool,
> or a separate utility? Can we add the entries directly, or should
> this be done via JMX?
Whatever is simplest. Which probably means "throw it into nodetool so
we don't ne
On Fri, Aug 24, 2012 at 3:39 PM, Eric Evans wrote:
> On Fri, Aug 24, 2012 at 11:27 AM, Jonathan Ellis wrote:
>> On Fri, Aug 24, 2012 at 11:23 AM, Eric Evans wrote:
>>> Actually, now that I think about it, I'd probably drop the entire
>>> notion of a "coordinator", and write the respective entiri
On Fri, Aug 24, 2012 at 11:27 AM, Jonathan Ellis wrote:
> On Fri, Aug 24, 2012 at 11:23 AM, Eric Evans wrote:
>> Actually, now that I think about it, I'd probably drop the entire
>> notion of a "coordinator", and write the respective entiries into a
>> column family in the system keyspaces. Each
On Fri, Aug 24, 2012 at 11:23 AM, Eric Evans wrote:
> Actually, now that I think about it, I'd probably drop the entire
> notion of a "coordinator", and write the respective entiries into a
> column family in the system keyspaces. Each system could then work
> through their respective queue of re
On Tue, Aug 21, 2012 at 2:54 PM, Jonathan Ellis wrote:
> On Mon, Aug 20, 2012 at 4:55 PM, Eric Evans wrote:
>> Shuffling the ranges to create a random distribution from contiguous
>> ranges has the potential to move a *lot* of data around (all of it,
>> basically). Doing this in an optimal way w
On Mon, Aug 20, 2012 at 4:55 PM, Eric Evans wrote:
> Shuffling the ranges to create a random distribution from contiguous
> ranges has the potential to move a *lot* of data around (all of it,
> basically). Doing this in an optimal way would mean never moving a
> range more than once. Since it is
Hi all,
First off, the ground rules. :)
This is a development/design discussion. If you have general
questions about virtual nodes that don't pertain to this discussion,
please ask them in another thread, or on user@ and we'll get them
answered there.
BACKGROUND
Currently, an upgrade from 1.1.
