mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2024-12-27 23:22:09 +00:00
haproxy public development tree
ce6fc25b17
The abns_socket in seamless-reload regtest regularly fails in Travis-CI on smaller machines only (typically the ppc64le and sometimes s390x). The error always reports an incomplete HTTP header as seen from the client. And this can occasionally be reproduced on the minicloud ppc64le image when setting a huge file descriptors limit (1 million). What happens in fact is the following: depending on the binding order, some connections from the client might reach the TCP listener on the old instance and be forwarded to the ABNS listener of the second instance just being prepared to start up. But due to the huge number of FDs, setting them up takes slightly more time and the 20ms server timeout may expire before the new instance finishes its startup. This can result in an occasional 504, except that since the client timeout is the same as the server timeout, both sides are closed at the same time and the client doesn't receive the 504. In addition a second problem plugs onto this: by default http-reuse is enabled. Some requests being forwarded to the older instance will be sent over an already established connection. But the CPU used by the starting process using many FDs will be taken away from the older process, whose abns listener will not see a request for more than 20ms, and will decide to kill the idle client connection. At the same moment the TCP proxy forwards a request over this closing connection, it detects the close and silently closes the other side to let the client retry, which is detected by the vtest client as another case of empty header. This is easier to reproduce in VMs with few CPUs (2 or less) and some noisy neighbors such as a few spinning loops in background. Let's just increase this tests' timeout to avoid this. While a few ms are close to the scheduler's granularity, this test is never supposed to trigger the timeouts so it's safe to go higher without impacts on the test execution time. At one second the problem seems impossible to reproduce on the minicloud VMs. |
||
|---|---|---|
| .github | ||
| contrib | ||
| doc | ||
| ebtree | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitignore | ||
| .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)