|
I have a pretty simple ipvs config.
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 103.200.100.1:80 wrr persistent 1800
-> 103.75.25.85:80 Route 1 0 0
-> 103.75.25.76:80 Route 1 0 0
-> 103.75.25.75:80 Route 1 0 0
The stickyness works fine on the local server, however when it syncs
over to the backup, the timeout is wrong.
On master:
TCP 29:53 NONE 103.90.0.17:0 103.200.100.1:80 103.75.25.76:80
On slave:
TCP 02:57 NONE 103.90.0.17:0 103.200.100.1:80 103.75.25.76:80
Obviously there are instances when the backup connections timeout but
they are in place on the master, so in the event the master fails, the
slave doesn't have the connections in it's table.
Is there a workaround for this? Can I extend the timeout of synched
connections via sysctl or something?
David
|
