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 be a good place to start looking.
Hope that helps. Aaron On 7 Apr 2011, at 03:26, A J wrote: > 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 and 3 in europe. > Now, if I can help, I would like to have most of the traffic from my > california clients being handled by the west_coast nodes. But incase > the west_coast nodes are down or slow, the co-ordinator node can be > elsewhere. > > What is the best strategy to give different weight to different nodes, > where some nodes are preferred over the others. > > > Thanks. > > > On Tue, Apr 5, 2011 at 2:23 PM, Peter Schuller > <peter.schul...@infidyne.com> wrote: >>> 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 >>
