Hi there, continue with my loast question: We have a anti port exhaustion configuration with cookie stickness:
[...] option redispatch cookie NID insert preserve httponly secure domain .zhiyejing.com ... server n1_0 10.0.0.1:80 check cookie n1 weight 10 server n1_1 10.0.0.1:800 track n1_0 cookie n1 weight 10 server n1_2 10.0.0.1:801 track n1_0 cookie n1 weight 10 ... server n2_0 10.0.0.2:80 check cookie n2 weight 10 server n2_1 10.0.0.2:800 track n2_0 cookie n2 weight 10 server n2_2 10.0.0.2:801 track n2_0 cookie n2 weight 10 ... [...] With this configuration, when a request come with Cookie: NID=n1 and n1_0's source port has been exhausted, will HAProxy pickup and using n1_1 or n1_2 instead of the full n1_0 automatically? Or should I let HAProxy call "bind" explicitly using the "source" directive to help it detect that this is a port exhaustion error: [...] option redispatch cookie NID insert preserve httponly secure domain .zhiyejing.com ... server n1_0 10.0.0.1:80 check cookie n1 weight 10 source 10.0.0.100:1024-65534 server n1_1 10.0.0.1:800 track n1_0 cookie n1 weight 10 source 10.0.0.100:1024-65534 server n1_2 10.0.0.1:801 track n1_0 cookie n1 weight 10 source 10.0.0.100:1024-65534 ... server n2_0 10.0.0.2:80 check cookie n2 weight 10 source 10.0.0.100:1024-65534 server n2_1 10.0.0.2:800 track n2_0 cookie n2 weight 10 source 10.0.0.100:1024-65534 server n2_2 10.0.0.2:801 track n2_0 cookie n2 weight 10 source 10.0.0.100:1024-65534 ... [...] Thanks :-) -- Best Regards BaiYang [email protected] http://baiy.cn **** < END OF EMAIL > ****
