mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2024-12-20 18:50:08 +00:00
3d9266f414
This one started to randomly fail on me again and I could figure the problem. It mixes one checked server with one unchecked on in each backend, and tries to make sure that each checked server receives exactly one request. But that doesn't work and is entirely time- dependent because if the check starts before the client, a pure TCP check is sent to the server, which sees an aborted connection and makes the whole check fail. Here what is done is that we make sure that only the second server and not the first one is checked. The traffic is delivered to all first servers, and each HTTP server must always receive a valid HTTP request. In parallel, checks must not fail as they're delivered to dummy servers. The check doesn't fail anymore, even when started on a single thread at nice +5 while 8 processes are fighting on the same core to inject HTTP traffic at 25 Gbps, which used to systematically make it fail previously. Since it took more than one hour to fix the "expect" line for the stats output, I did it using a small script that I pasted into the vtc file in case it's needed later. The relevance of this test is questionable once its complexity is factored in. Let's keep it as long as it works without too much effort. |
||
|---|---|---|
| .. | ||
| 1be_40srv_odd_health_checks.vtc | ||
| 4be_1srv_health_checks.vtc | ||
| 4be_1srv_smtpchk_httpchk_layer47errors.vtc | ||
| 40be_2srv_odd_health_checks.vtc | ||
| agent-check.vtc | ||
| common.pem | ||
| http-check-expect.vtc | ||
| http-check-send.vtc | ||
| http-check.vtc | ||
| http-monitor-uri.vtc | ||
| ldap-check.vtc | ||
| mysql-check.vtc | ||
| pgsql-check.vtc | ||
| redis-check.vtc | ||
| smtp-check.vtc | ||
| spop-check.vtc | ||
| ssl-hello-check.vtc | ||
| tcp-check_min-recv.vtc | ||
| tcp-check_multiple_ports.vtc | ||
| tcp-check-ssl.vtc | ||
| tcp-checks-socks4.vtc | ||
| tls_health_checks.vtc | ||