mirror of
https://github.com/haproxy/haproxy.git
synced 2026-04-20 22:01:49 -04:00
HAProxy - Load balancer
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. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README | ||
| ROADMAP | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - BRANCHES to understand the project's life cycle and what version to use - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)