@rockandska wrote:
Hi,
Similar to #2134
Despite it is the same error and the same fix, i don’t use
resolversin my conf# haproxy -v HA-Proxy version 1.7.5-2 2017/05/17backend bk_redis mode tcp option tcp-check #tcp-check connect --> comment it solved the problem tcp-check send PING\r\n tcp-check expect string +PONG tcp-check send info\ replication\r\n tcp-check expect string role:master tcp-check send QUIT\r\n tcp-check expect string +OK server redis-1-debian-9 redis-1-debian-9:6379 check inter 1s server redis-2-debian-9 redis-2-debian-9:6379 check inter 1s server redis-3-debian-9 redis-3-debian-9:6379 check inter 1sBut when i read the doc, it clearly state that
tcp-check connectis requiredIn a tcp-check ruleset a 'connect' is required, it is also mandatory to start the ruleset with a 'connect' rule. Purpose is to ensure admin know what they do.
- Why
tcp-check connectfail ? bug ?- Despite what the doc says, is it ok to remove
tcp-check connect? what is the implication of this choice ?- Since we don’t have the problem with the exact same conf with v1.5.18 (centos7 ), could we remove it on this version too to have the same config on 1.5.18 and 1.7.5 ?
Regards,
Posts: 1
Participants: 1