Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of eevans@acunu.com designates
 209.85.212.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CCEC9F09.85B2%mkjellman@barracuda.com>
References: 
 <CAEONjQJb-bxrjaEZQkurWSO_xkCHdaAaqFAEyyqkk_4vm9CfJw@mail.gmail.com>
	<CCEC9F09.85B2%mkjellman@barracuda.com>
Date: Wed, 12 Dec 2012 15:15:41 +0000
Message-ID: 
 <CAL35Oi0=RoXojssb2LJfeA7xxYANyKn3b-Nkd8PjV6ZLYW8nuQ@mail.gmail.com>
Subject: Re: Vnode migration path
From: Eric Evans <eevans@acunu.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Dec 11, 2012 at 4:28 PM, Michael Kjellman
<mkjellman@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 <rlow@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 <mkjellman@barracuda.com> wro=
te:
>>
>> 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 eac=
h
>> 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
>   =AD=AD


--
Eric Evans
Acunu | http://www.acunu.com | @acunu