On Thu, Dec 5, 2013 at 8:31 AM, Andre Sprenger <andre.spren...@getanet.de>wrote:
> We just migrated a Cassandra cluster on EC2 to another instance type. We > replaced one server after another, this creates problems similar to what > you describe. > > We simply stop Cassandra, copy the complete data dir to an EBS volume, > terminate the server, launch another server with the same IP, copy the data > dir from the EBS volume and start Cassandra on the new server. > You don't even need to keep the same IP to do this operation. https://engineering.eventbrite.com/changing-the-ip-address-of-a-cassandra-node-with-auto_bootstrapfalse/ =Rob
