Current versions of Hector will mark the host as temporarily down if a
connection times out (retrying N seconds later; defaults to 10). If
you only have one host in your list, this will be an issue. It would
be a good idea to use more than one VIP for this reason.
Managing configurations on the ap
Thanks guys.
On Dec 20, 2010, at 5:44 PM, Dave Viner wrote:
> You can put a Cassandra cluster behind a load balancer. One thing to be
> cautious of is the health check. Just because the node is listening on port
> 9160 doesn't mean that it's healthy to serve requests. It is required, but
You can put a Cassandra cluster behind a load balancer. One thing to be
cautious of is the health check. Just because the node is listening on port
9160 doesn't mean that it's healthy to serve requests. It is required, but
not sufficient.
The real test is the JMX values.
Dave Viner
On Mon, D
You will loose part of the retry / fallback functionality offered by hector.
The job of the client lib is not only load-balancing. I.e. if a node is
bootstrapping it will accept TCP connections but throw an exception which will
be communicated via thrift. The client lib is supposed to handle tha
