On 9/21/09 1:28 PM, Stefan wrote:
Hello
Am Montag 21 September 2009 20:59:01 schrieb Hank A. Paulson:
I think you are getting a new cookie because of how your openais/etc is
failing over, not haproxy. haproxy doesn't create the cookie it just passes
it along.
drbd/openais doesn't have a way
I think you are getting a new cookie because of how your openais/etc is
failing over, not haproxy. haproxy doesn't create the cookie it just passes it
along.
drbd/openais doesn't have a way to maintain the same tcp connection id across
failovers (AFAIK), so when you fail over you get a new
Hello
Am Montag 21 September 2009 20:59:01 schrieb Hank A. Paulson:
I think you are getting a new cookie because of how your openais/etc is
failing over, not haproxy. haproxy doesn't create the cookie it just passes
it along.
drbd/openais doesn't have a way to maintain the same tcp
Hi,
On Mon 21.09.2009 22:28, Stefan wrote:
Hello
Am Montag 21 September 2009 20:59:01 schrieb Hank A. Paulson:
I think you are getting a new cookie because of how your openais/etc
is failing over, not haproxy. haproxy doesn't create the cookie it
just passes it along.
I understood haproxy
4 matches
Mail list logo