On Tue, Dec 11, 2012 at 4:28 PM, Michael Kjellman <mkjell...@barracuda.com> wrote: > Awesome (and very welcomed news), what kind of failure conditions can we > expect if a node goes down during the migration?
A shuffle is just a bunch of moves mapped out ahead of time, and worked through by each node incrementally. These mappings are persisted, so a node that went down during a shuffle would simply pick back up where it left off when it came back online. A node irrecoverably failing mid-shuffle would likely require some intervention to sort out. Either way, there won't be any other impact to the cluster beyond what is normally caused by a down node. > From: Richard Low <r...@acunu.com> > Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org> > Date: Tuesday, December 11, 2012 3:33 AM > To: "user@cassandra.apache.org" <user@cassandra.apache.org> > Subject: Re: Vnode migration path > > Hi Mike, > > There's also the shuffle utility (in the bin directory) that can > incrementally move ranges around to migrate to vnodes. > > Richard. > > > On 11 December 2012 08:47, Michael Kjellman <mkjell...@barracuda.com> wrote: >> >> So I'm wondering if anyone has given thought to their migration path to >> Vnodes. Other than having a separate cluster and migrating the data from the >> old cluster to the vnode cluster what else can we do. >> >> One suggestion I've heard is start up a second Cassandra instance on each >> node on different ports and migrate between nodes that way. >> >> Best, >> mike >> >> 'Like' us on Facebook for exclusive content and other resources on all >> Barracuda Networks solutions. >> >> Visit http://barracudanetworks.com/facebook >> >> >> >> > > > > -- > Richard Low > Acunu | http://www.acunu.com | @acunu > > ---------------------------------- > 'Like' us on Facebook for exclusive content and other resources on all > Barracuda Networks solutions. > Visit http://barracudanetworks.com/facebook > -- Eric Evans Acunu | http://www.acunu.com | @acunu
