From 734b540aa33b4f55c5a542cb3acf06050cd0d576 Mon Sep 17 00:00:00 2001 From: Sundaresan Rajangam Date: Thu, 8 Dec 2016 18:26:24 -0800 Subject: [PATCH] Remove tcp-check connect option for redis on haproxy tcp-check connect option for redis on haproxy.cfg causes the client connections in the redis-server to grow continuously and reaches the max limit resulting in connection failure/response error for requests from collector and other analytics services to redis. Change-Id: If088ba40e7f0bc420a753ec11bca9dd081ffb160 Partial-Bug: #1648601 (cherry picked from commit 32388a96b848629bf8f4b7d7ea832fca8c3dccd9) --- fabfile/templates/collector_haproxy.py | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/fabfile/templates/collector_haproxy.py b/fabfile/templates/collector_haproxy.py index 403ea5d19..d38f61db5 100644 --- a/fabfile/templates/collector_haproxy.py +++ b/fabfile/templates/collector_haproxy.py @@ -12,10 +12,8 @@ backend contrail-analytics-api option nolinger + timeout server 3m balance roundrobin - option tcp-check - tcp-check connect port 6379 - default-server error-limit 1 on-error mark-down $__contrail_analytics_api_backend_servers__ #contrail-collector-marker-end