cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Coli <>
Subject Re: Replacing a Node using a Replication
Date Thu, 05 Dec 2013 18:56:43 GMT
On Thu, Dec 5, 2013 at 8:31 AM, Andre Sprenger <>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.


View raw message