Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cassandra-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of jbellis@gmail.com designates
 209.85.220.214 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=MKADHfUwfimEcZBSuiuNNNfzcfZ7yjsMFCR+WhQZJm/iZKIEo50oeMFQjSVNtXhVZt
         YURrb0i+nHHmBMnKdQS37fY6ZxOHM+v3jAdfsrgZK424YnASUZ6GeKSyHZu9I/RQOBh9
         7a+FSsmfWDs3pXkULNk1fw+4h9sEXD6akJCr4=
MIME-Version: 1.0
In-Reply-To: <20091119191316.GA70591@alumni.caltech.edu>
References: <cd6ea56f0911181005x15170794t4e265e1b375ebb92@mail.gmail.com>
	<e06563880911181030j74b2e180kd93c0576a64772b2@mail.gmail.com>
	<a1625f290911181100l60969355jd0234e75017ed5e9@mail.gmail.com>
	<e06563880911181103n7df47a47j7e297c42fd58725d@mail.gmail.com>
	<f0ed03e30911181147m1304cf04m868d4f5e7ca1d389@mail.gmail.com>
	<e06563880911181150k6eb45e2ase82fc2ab43fc1620@mail.gmail.com>
	<20091119191316.GA70591@alumni.caltech.edu>
From: Jonathan Ellis <jbellis@gmail.com>
Date: Thu, 19 Nov 2009 13:17:16 -0600
Message-ID: <e06563880911191117g4d1c4ddau58a4510afaa0b838@mail.gmail.com>
Subject: Re: Cassandra backup and restore procedures
To: cassandra-user@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Currently, no.  Feel free to open a ticket.  It would be fairly easy
to make the decommission code in trunk handle this.

On Thu, Nov 19, 2009 at 1:13 PM, Anthony Molinaro
<anthonym@alumni.caltech.edu> wrote:
> So, is there anyway to recover if you can't guarantee the same IP address=
?
> Since we are running on EC2 (as I'm sure are others on the list), and the=
re
> is no way to make this guarantee.
>
> Is this sort of recoverability on the roadmap anywhere?
>
> Thanks,
>
> -Anthony
>
> On Wed, Nov 18, 2009 at 01:50:20PM -0600, Jonathan Ellis wrote:
>> No, bootstrap is currently only for adding new nodes, not replacing dead=
 ones.
>>
>> On Wed, Nov 18, 2009 at 1:47 PM, Simon Smith <simongsmith@gmail.com> wro=
te:
>> > I'm sorry if this was covered before, but if you lose a node and
>> > cannot bring it (or a replacement) back with the same IP address or
>> > DNS name, is your only option to restart the entire cluster? =A0E.g. i=
f
>> > I have nodes 1, 2, and 3 with replication factor 3, and then I lose
>> > node 3, is it possible to bring up a new node 3 with a new IP (and a
>> > Seed of either node 1 or node 2) and bootstrap it?
>> >
>> > Thanks,
>> >
>> > Simon
>> >
>> > On Wed, Nov 18, 2009 at 2:03 PM, Jonathan Ellis <jbellis@gmail.com> wr=
ote:
>> >> Tokens can change, so IP is used for node identification, e.g. for
>> >> hinted handoff.
>> >>
>> >> On Wed, Nov 18, 2009 at 1:00 PM, Ramzi Rabah <rrabah@playdom.com> wro=
te:
>> >>> Hey Jonathan, why should a replacement node keep the same IP
>> >>> address/DNS name as the original node? Wouldn't having the same toke=
n
>> >>> as the node that went down be sufficient (provided that you did the
>> >>> steps above of copying the data from the 2 neighboring nodes)?
>> >>>
>> >
>
> --
> ------------------------------------------------------------------------
> Anthony Molinaro =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <ant=
honym@alumni.caltech.edu>
>