I think that was a bit hyperbolic, but affinity does have drawbacks. Balancing the requests is much easier without affinity, and you don't run the risk of the load ever getting severely skewed. Maintenance is also easier, because you don't have to "drain" the load from a server, you just drop it out of service, and the requests can go on to something else.
The latter point isn't that big a deal if the only reason for affinity is SSL session caching, because you could yank the server even if it has active sessions, and the clients would simply re-establish with the next backend.
I often load-balance ssl using session affinity, and would also like to know if this author has encountered other issues, or just hasn't looked at the capabilities of haproxy in a while.
The latter point isn't that big a deal if the only reason for affinity is SSL session caching, because you could yank the server even if it has active sessions, and the clients would simply re-establish with the next backend.
I often load-balance ssl using session affinity, and would also like to know if this author has encountered other issues, or just hasn't looked at the capabilities of haproxy in a while.