incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Coli <rc...@eventbrite.com>
Subject Re: listen_address and rpc_address address on different interface
Date Fri, 12 Jul 2013 00:38:04 GMT
On Thu, Jul 11, 2013 at 2:53 AM, Christopher Wirt <chris.wirt@struq.com>wrote:

> **
>
> If we were to take down a node and change the listen address then re-join
> the ring, the other nodes will mark the node as dead when we take it down
> and assume we have a new node when we bring it back on a different address.
>
**
>
> Lots of wasted rebalancing and compaction will start.****
>
> We use Cassandra 1.2.4 w/vnodes.****
>
>
In theory you can :

1) stop cassandra
2) change ip/config/etc.
3) restart cassandra with auto_bootstrap=false in cassandra.yaml

I believe this should "just work" because the node knows what tokens it is
claiming from the system keyspace, it simply announces to the cluster that
it is now responsible for each of those ranges. The other nodes say should
just say "ok".

If you do this, please let us know the results! Obviously you should try it
first on a non-production cluster...

So back to question one, am I wasting my time?
>

My hunch is "probably" but it is just a hunch.

=Rob

Mime
View raw message