(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/3045 github. org/Juniper/ contrail- controller/ commit/ d520c323c44d07e 011d9a83e55e016 eb253d929d
Committed: http://
Submitter: Zuul
Branch: master
commit d520c323c44d07e 011d9a83e55e016 eb253d929d
Author: Sundaresan Rajangam <email address hidden>
Date: Tue Sep 23 12:31:56 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: Ie8e14e698ccfec 537827c95b05568 1c8268a5fba