We tried using HAProxy (to force connections to the closest datacenter)
instead of relying on Hector to do the right thing and had problems with
it. The client libraries we have used are smart enough to handle the node
up/down case, and in most scenarios, if there is a slow node, they will
route ar
I think you are going to be creating problems that the drivers were designed
to avoid, it is not a good idea in general.
/je
On Jun 27, 2014, at 11:28 AM, Serge Fonville wrote:
> Hector is same way, if any node is slow to responds, times out or dies hector
> will remove it from the pool leavin
>
> Hector is same way, if any node is slow to responds, times out or dies
> hector will remove it from the pool leaving making it look like cluster
> dead. The entire fault tolerant part of cassandra would be lost.
Does this still apply if all nodes contain all data?
Kind regards/met vriendelijk
Hector is same way, if any node is slow to responds, times out or dies hector
will remove it from the pool leaving making it look like cluster dead. The
entire fault tolerant part of cassandra would be lost.
Chris
On Jun 27, 2014, at 11:00 AM, Michael Dykman wrote:
> NO, really it can't. I k
NO, really it can't. I know little of Hector, but when using the
datastax driver, Cassandra provides a highly available set of
connections; a single Cassandra session will have explicit connections
to all of the node which make up a given cluster.
The Cassandra server itself relies on a lot of cr
