Hi Will,

>From your configuration, the application server is supposed to setup
the SIMULATE_STICKY_SESSION.
Can you confirm it is the case?

Baptiste

On Thu, May 23, 2013 at 1:11 PM, Will Glass-Husain <[email protected]> wrote:
> Hi,
>
> I'm running haproxy-ss-20130509.  I have load balancing set up with a stick
> table using an application-generated sticky session cookie.  This running on
> two haproxy instances (with an Amazon ELB front-end).
>
> I'm noticing that the server will occasionally change a mapping from one
> server to another for no apparent reason.  In other words, a given cookie
> value will go to server app1, and then later it will switch over to app2.
> The log doesn't show a DOWN message for app1.
>
> What might the cause of this be?  As I read the docs, the entries in the
> stick-table are supposed to expire only after idle time - is that correct?
>
> peers balancers
>     peer balancer1 10.0.2.85:1024
>     peer balancer2 10.0.3.174:1024
>
> backend simulate
>     option httpchk OPTIONS /simulate/api/status
>     stick-table type string len 40 size 5M expire 120m peers balancers
>     stick store-response set-cookie(SIMULATE_STICKY_SESSION) table simulate
>     stick on cookie(SIMULATE_STICKY_SESSION) table simulate
>     stick on url_param(SIMULATE_STICKY_SESSION,;) table simulate
>
>     server app1 10.0.2.11:8080  cookie app1 check inter 10000
>     server app2 10.0.3.11:8080  cookie app2 check inter 10000
>
> Best, WILL

Reply via email to