commit 4524220f82cb25e13f6213bdc110f399521cc3b3
Author: Sanju Abraham <email address hidden>
Date: Wed Jun 1 00:02:37 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/20828 github. org/Juniper/ contrail- provisioning/ commit/ 4524220f82cb25e 13f6213bdc110f3 99521cc3b3
Committed: http://
Submitter: Zuul
Branch: R3.0
commit 4524220f82cb25e 13f6213bdc110f3 99521cc3b3
Author: Sanju Abraham <email address hidden>
Date: Wed Jun 1 00:02:37 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: I3087893b0501d4 1cedf5eb89a6b71 f7e38f5a0d0