haproxy tcp-check is failing on last server

Solution In Progress - Updated -

Issue

  • When there are multiple tcp-connect port servers specified in the backend, the lasttcp-check is never validated.

  • Example haproxy configuration:

backend test1
    mode tcp
    option tcp-check
    tcp-check connect port 4568
    tcp-check connect port 6790
    server  server1 10.0.0.2:4567 check inter 500ms
    server  server2 10.0.0.3:4567 check inter 500ms
    server  server3 10.0.0.4:4567 check inter 500ms       
  • As a result, haproxy does not perform health check on the last tcp-check listed server, and never removes the server from the backend server group even if there is an issue.

Environment

  • Red Hat Enterprise Linux (RHEL) 7.7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content