On Fri, Aug 24, 2012 at 3:39 PM, Eric Evans eev...@acunu.com wrote:
On Fri, Aug 24, 2012 at 11:27 AM, Jonathan Ellis jbel...@gmail.com wrote:
On Fri, Aug 24, 2012 at 11:23 AM, Eric Evans eev...@acunu.com wrote:
Actually, now that I think about it, I'd probably drop the entire
notion of a
On Mon, Aug 27, 2012 at 3:54 PM, Eric Evans eev...@acunu.com 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
On Fri, Aug 24, 2012 at 11:23 AM, Eric Evans eev...@acunu.com 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
On Fri, Aug 24, 2012 at 11:27 AM, Jonathan Ellis jbel...@gmail.com wrote:
On Fri, Aug 24, 2012 at 11:23 AM, Eric Evans eev...@acunu.com 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
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
