cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Wirt" <>
Subject listen_address and rpc_address address on different interface
Date Thu, 11 Jul 2013 09:53:17 GMT


I was wondering if anyone has measured the performance improvements to
having the listen address and client address bound to different interface?


We a have 2gbit connection serving both at the moment and this doesn't come
close to being saturated. But being very keen on fast reads at the 99th
percentile we're interested in even the smallest improvements.


Next question - Has anyone ever moved an existing node to have the listen
address and client access address bound to different addresses?


Our Problem  

Currently our only address is a DNS entry which we would like to keep bound
to the client access.

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.

Not sure there will be anyway around this.

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







View raw message