Because you create a bottleneck at the HAProxy and because the presence of the proxy precludes clients properly backing off from nodes returning errors. The proper approach is to have clients maintain connection pools with connections to multiple nodes in the cluster, and then to spread requests across those connections. Should a node begin returning errors (for example, because it is overloaded), clients can remove it from rotation.
On Sat, Aug 28, 2010 at 11:27 AM, Mark <static.void....@gmail.com> wrote: > On 8/28/10 11:20 AM, Benjamin Black wrote: >> >> no and no. >> >> On Sat, Aug 28, 2010 at 10:28 AM, Mark<static.void....@gmail.com> wrote: >>> >>> I will be loadbalancing between nodes using HAProxy. Is this >>> recommended? >>> >>> Also is there a some sort of ping/health check uri available? >>> >>> Thanks >>> > any reason on why loadbalancing client connections using HAProxy isnt > recommended? >
