Cassandra handles nodes changing IP. The import thing to Cassandra is the
token, not the IP.
In your case did the replacement node have the same token as the failed one?
You can normally work around these issues using commands like nodetool
removetoken.
Cheers
-
Aaron
When my EC2 instance failed I restarted it, and added the new private IP
address to the list of seed nodes (was this my error?).
Nodetool then showed 4 live nodes and one dead one (corresponding to the
old private IP address).
I'm guessing that what I should have done on the restarted node is
How do I configure my cluster to run in EC2? In my cassandra.yaml I have
IP addresses under seed_provider, listen_address and rpc_address.
I tried setting up my cluster using just the EC2 private addresses but when
one of my instances failed and I restarted it there was a new private
address.
You have to use private IPs, but if an instance dies you have to bootstrap
it with replace token flag. If you use EC2 I'd recommend Netflix's Priam
tool. It manages all that stuff, plus you have S3 backup.
Andrey
On Mon, Feb 11, 2013 at 11:35 AM, Brian Tarbox tar...@cabotresearch.comwrote:
