(1) When Heart beat to the discovery server fails [haproxy down/not started], the discovery client library marks the Discovery connection as DOWN.
However, on successful Heart beat, the connection status is not being marked UP. Also, reset the connection status to DOWN when the response code for
HeartBeat request is not 200.
(2) Increasing the timeout for introspect connection in contrail-status to 0.5 seconds.
In swisscom setup, changing the timeout from 0.01 to 0.1 did not work. Did not see much load on the system. Changing the timeout to 0.5 to be on the safer side.
Closes-Bug: #1372875
Reviewed: https:/ /review. opencontrail. org/3064 github. org/Juniper/ contrail- controller/ commit/ 26810947dec2267 7f75bbe0579b960 ccf38aec5d
Committed: http://
Submitter: Zuul
Branch: R1.10
commit 26810947dec2267 7f75bbe0579b960 ccf38aec5d
Author: Sundaresan Rajangam <email address hidden>
Date: Wed Sep 24 01:35:05 2014 -0700
(1) When Heart beat to the discovery server fails [haproxy down/not started], the discovery client library marks the Discovery connection as DOWN.
However, on successful Heart beat, the connection status is not being marked UP. Also, reset the connection status to DOWN when the response code for
HeartBeat request is not 200.
(2) Increasing the timeout for introspect connection in contrail-status to 0.5 seconds.
In swisscom setup, changing the timeout from 0.01 to 0.1 did not work. Did not see much load on the system. Changing the timeout to 0.5 to be on the safer side.
Closes-Bug: #1372875
Change-Id: I90fa290beac079 b25781d5c2ac2db 0d5193c0828