I would look at your client and see if it can handle multiple pools. So it will
try to connect in the first pool, if that fails retry the other nodes in that
pool and then move to the next pool. I think hector has grabbed some of the
performance detection features from the DynamicSnitch so may b
-org.3065146.n2.nabble.com/LB-scenario-tp6224754p6246968.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
I have done some more research. My question now is:
1. From my tests I see that it matters a lot whether the co-ordinator
node is local (geographically) to the client or not.
I will have a cassandra cluster where nodes will be distributed across
the globe. Say 3 in US east_cost, 3 in US west_coast
> Can someone comment on this ? Or is the question too vague ?
Honestly yeah I couldn't figure out what you were asking ;) What
specifically about the diagram are you trying to convey?
--
/ Peter Schuller
AJ,
One issue that I found in using load balancer in front of cassandra nodes is
that a single node might become bogged down by compaction, or other actions
unrelated to the client. If the load balancer does not pick this up in
time, it might route client requests to the node that is temporarily
Can someone comment on this ? Or is the question too vague ?
Thanks.
On Wed, Mar 30, 2011 at 3:58 PM, A J wrote:
> Does the following load balancing scenario look reasonable with cassandra ?
> I will not be having any app servers.
>
> http://dl.dropbox.com/u/7258508/2011-03-30_1542.png
>
> Thank
Does the following load balancing scenario look reasonable with cassandra ?
I will not be having any app servers.
http://dl.dropbox.com/u/7258508/2011-03-30_1542.png
Thanks.
