I'm not going to be on Amazon, but I'm planning to use hostnames instead of IP's and a dynamically generated /etc/hosts file and I think that would deal with this problem. I'm sure a private DNS server would be just as good.
My real motive in saying this is so someone will scream at me if I'm wrong and save me the time of exploring the bad solution. :-). Tim Freeman Email: tim.free...@hp.com Desk in Palo Alto: (650) 857-2581 Home: (408) 774-1298 Cell: (408) 348-7536 (No reception business hours Monday, Tuesday, and Thursday; call my desk instead.) -----Original Message----- From: Anthony Molinaro [mailto:antho...@alumni.caltech.edu] Sent: Thursday, November 19, 2009 11:14 AM To: cassandra-user@incubator.apache.org Subject: Re: Cassandra backup and restore procedures 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 there 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 <simongsm...@gmail.com> wrote: > > 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? E.g. if > > 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 <jbel...@gmail.com> wrote: > >> 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 <rra...@playdom.com> wrote: > >>> Hey Jonathan, why should a replacement node keep the same IP > >>> address/DNS name as the original node? Wouldn't having the same token > >>> 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 <antho...@alumni.caltech.edu>
