commit 3f2029f3ea72e46d886f0f2c2660f9f26aeee44d
Author: Sanju Abraham <email address hidden>
Date: Tue May 31 23:48:02 2016 -0700
All client connecting to analytics api need to use the VIP if deployed in a HA setup.
The VIP on the LB node is what should recevive requests and proxy those to the backends.
Since cluster monitor will ensure that all TCP connections are on the active LB especially
after failures, any stale connections on the standby LB is forcefully reset.
With Anycast VIP, the reset will not happen as each LB instance will be able to proxy requests
to backends.
Reviewed: https:/ /review. opencontrail. org/20825 github. org/Juniper/ contrail- provisioning/ commit/ 3f2029f3ea72e46 d886f0f2c2660f9 f26aeee44d
Committed: http://
Submitter: Zuul
Branch: master
commit 3f2029f3ea72e46 d886f0f2c2660f9 f26aeee44d
Author: Sanju Abraham <email address hidden>
Date: Tue May 31 23:48:02 2016 -0700
All client connecting to analytics api need to use the VIP if deployed in a HA setup.
The VIP on the LB node is what should recevive requests and proxy those to the backends.
Since cluster monitor will ensure that all TCP connections are on the active LB especially
after failures, any stale connections on the standby LB is forcefully reset.
With Anycast VIP, the reset will not happen as each LB instance will be able to proxy requests
to backends.
Closes Bug: #1578847
Change-Id: If2b41876dcff97 6e14e3fa87dcb78 40be928cec4