- 16 Oct, 2018 40 commits
-
-
Poul-Henning Kamp authored
If the worker pool is configured too small, it can deadlock. Recovering from this would require a lot of complicated code, to discover queued but unscheduled tasks which can be cancelled (because the client went away or otherwise) and code to do the cancelling etc. etc. But fundamentally either people configured their pools wrong, in which case we want them to notice, or they are under DoS, in which case recovering gracefully is unlikely be a major improvement over a restart. Instead we implement a per-pool watchdog and kill the child process if nothing has been dequeued for too long. Default value 10 seconds, open to discussion. Band-aid for: #2418 Test-case by: @Dridi
-
Poul-Henning Kamp authored
(Same as we do in H1) Fixes #2589
-
Poul-Henning Kamp authored
Spotted by: Willy Tarreau <w@1wt.eu>
-
Dridi Boukelmoune authored
Fixes #2787
-
Nils Goroll authored
Checking and preparing our worker struct does not need to happen under the lock.
-
Nils Goroll authored
Over time, I have repeatedly stared at this code again and again wondering if (and why) our cv signaling is correct, just to end up with the same insight each time (but first overlooking #2719) Being fully aware that we do not want to plaster our code with outdated comments, I hope this explanation is warranted to save myself (and others, hopefully) from wasting precious life time on reiterating over the same question.
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
Fixes: #2782
-
Emmanuel Hocdet authored
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
Take 2. Let's see if this time sticks.
-
Poul-Henning Kamp authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Geoff Simmons authored
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
-
Federico G. Schwindt authored
-
Dag Haavi Finstad authored
This adds -Wno-implicit-fallthrough for libvgz to satisfy gcc7. The -Wno-unknown-warning-option is there to satisfy older gcc/clang that don't recognize -Wno-implicit-fallthrough.
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
Fixes: #2668
-
Poul-Henning Kamp authored
This eliminates read-add-zero-write on counters outside this group.
-
Poul-Henning Kamp authored
in VSC_C_main and protect them with the ban-mtx.
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
Conflicts: lib/libvcc/generate.py
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-
Dridi Boukelmoune authored
-
Poul-Henning Kamp authored
reports stuff from it for debugging.
-
Poul-Henning Kamp authored
-
Poul-Henning Kamp authored
-