Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am interested in using haproxy for load-balancing with sticky session support, but using stick tables directly to benefit from upcoming master/master stick table replication in haproxy 1.5.

As a simple example, let's assume I have one load balancer LB1, and two backends A and B. LB1 can load balance between A and B (same IP, different ports in this test config), but it should stick all requests from one session to the same backend. Session are defined as a uri parameter, e.g. http://example.com/foo?JSESSIONID=session_id.

Something as follows works perfectly:

listen m1 192.168.122.2:80
    mode http
    balance roundrobin
    appsession JSESSIONID len 64 timeout 1h request-learn mode query-string
    server webA 192.168.3.68:8088 cookie A check
    server webB 192.168.3.68:8089 cookie B check

but I would like to get the same behavior using the lower level stick table(s) so that multiple load balancers can synchronize each other.

share|improve this question

migrated from stackoverflow.com Dec 9 '10 at 17:14

This question came from our site for professional and enthusiast programmers.

1 Answer 1

up vote 0 down vote accepted

This is actually not implemented yet in haproxy. I made a temporary fix to do this until a more flexible method is integrated into haprxoy on github

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.