- 07 Dec, 2016 1 commit
-
-
Federico G. Schwindt authored
Fixes #2148.
-
- 05 Dec, 2016 3 commits
-
-
Martin Blix Grydeland authored
Increase the Nagle-avoidance delay in r02035.vtc to make the test case less timing sensitive.
-
Martin Blix Grydeland authored
HTC_RxInit and HTC_RxReInit could write a single '\0' NUL character outside of the workspace when its called and there is zero bytes left in the workspace. This would trigger the workspace canary causing subsequent assertion. Fix by releaving HTC_RxInit and HTC_RxReInit of adding the '\0' character. HTC_RxStuff and V1F_FetchRespHdr returns HTC_S_OVERFLOW if the available buffer space is zero. Both make sure to insert the '\0' character just before calling the completion check function. Note that this fix does not change the fact that we have exchausted the workspace and are unable to continue. Varnishd will panic nonetheless, but at least we have not stepped out of our boundries. Ref: #1834
-
Martin Blix Grydeland authored
Make sure that the workspace can accomodate the pipelined data before memmoving it into place in SES_RxReInit.
-
- 01 Dec, 2016 1 commit
-
-
Pål Hermunn Johansen authored
-
- 28 Nov, 2016 3 commits
-
-
Pål Hermunn Johansen authored
-
Martin Blix Grydeland authored
When doing range delivery, make the delivery processing finish early when all of the bytes of the requested range has been delivered. This to avoid waiting around for a slow fetch to finish before handling the next request on the connection. Fixes: #2035
-
Martin Blix Grydeland authored
A delivery processor may want to finish the delivery early. Change the return value from VDP_bytes and the delivery processors into 3 categories. 0 means continue, negative is error and positive is finished. The latching of errors (to help ESI delivery continue while still recording the error) will latch the lowest non-zero value observed. VDP_gunzip is fixed to not unconditionally return errors. Also add some text to explain the behaviour of VDP_bytes and its delivery processors.
-
- 24 Nov, 2016 1 commit
-
-
Pål Hermunn Johansen authored
-
- 23 Nov, 2016 1 commit
-
-
Pål Hermunn Johansen authored
-
- 22 Nov, 2016 5 commits
-
-
Nils Goroll authored
(backend tasks for the time being) Add parameter thread_pool_reserve to tweak Conflicts: bin/varnishd/mgt/mgt_pool.c
-
Nils Goroll authored
-
Nils Goroll authored
We should queue bo tasks to avoid failing client requests unnecessarily. The detailed parameter description of the queue_limit was already correct, improve the short one.
-
Nils Goroll authored
The nthr => wthread_min assertion could trigger if wthread_min was changed after the first comparison.
-
Nils Goroll authored
Previously, after sending a thread to varnish heaven, the herder slept for wthread_destroy_delay unconditionally. Instead, we now wait on the cv so we get woken up in case we run dry during the delay. This change is relevant proportionally to the value of wthread_destroy_delay if the spread between thread_pool_min and thread_pool_max is big and varnish is exposed to sudden traffic peaks. IOW, it will probably be only relevant for high performance setups. Also, we now sleep for thread_pool_timeout unless a shorter delay is warranted. This will delay the effect of thread parameter changes for up to thread_pool_timeout seconds unless the pool runs dry, in which case they will become effective immediately.
-
- 18 Nov, 2016 1 commit
-
-
Nils Goroll authored
doc-fixes #2129
-
- 17 Nov, 2016 3 commits
-
-
Nils Goroll authored
For epoll, we tolerate spurious reports, for all other waiters we assert. fixes #2117 Conflicts: bin/varnishd/waiter/cache_waiter_epoll.c
-
Dridi Boukelmoune authored
Fixes #1899 Closes #2110
-
Dridi Boukelmoune authored
Ramp up from simple tokens to here documents. Conflicts: doc/sphinx/reference/varnish-cli.rst
-
- 16 Nov, 2016 3 commits
-
-
Martin Blix Grydeland authored
When checking the timestamps on deleting a session, allow up to clock_step seconds error before bailing. Fixes: #1874
-
Martin Blix Grydeland authored
This value is used in calculations that could reveal clock step, specifying the amount of error we allow before panicking. It defaults to a conservative 1 second.
-
Martin Blix Grydeland authored
Show both the real and the monotonic time in the panic output when the panic is created. This is useful to have something to compare other panic timestamps against. The existing timestamp in the panic output is recorded by the management process at the time of receiving the panic from the child process. Due to processing and possible core dump creation, this time isn't very useful for comparison purposes.
-
- 25 Oct, 2016 1 commit
-
-
Poul-Henning Kamp authored
Spotted & prodded by: Hermunn Closes: #2026
-
- 21 Oct, 2016 1 commit
-
-
Federico G. Schwindt authored
Use MGT_complain() to log any errors; we might have a better chance to understand what's going in. Fixes #2115.
-
- 13 Oct, 2016 4 commits
-
-
Dridi Boukelmoune authored
When we renamed resp.msg to resp.reason to match RFC and VCL terminology we forgot to rename its counterpart. Instead of renaming -msg to -reason the former will instead become an alias of the latter. This way it can be applied to older branches (modulus inline documentation).
-
Pål Hermunn Johansen authored
-
Pål Hermunn Johansen authored
-
Nils Goroll authored
(Backport of 2bbcde1d with the fix b698aec2 squashed in) doc fixes #2107
-
- 12 Oct, 2016 4 commits
-
-
Pål Hermunn Johansen authored
Updated error message in MGT_Child_Cli_Fail to indicate that we actually have sent the kill signal to the child process.
-
Pål Hermunn Johansen authored
A new jail level, JAIL_MASTER_KILL, is introduced. The mgt process takes this level before killing the child process. Fixes: #2010
-
Pål Hermunn Johansen authored
A new function, kill_child() is introduced, so that kill() is only called from this function. This is a preparation of fixing the jail implementation.
-
Pål Hermunn Johansen authored
There seems to be an error in the varnish jail design, which makes the mgt process uable to kill the child process. To confirm this, add some error checking to the relevant code. Related to: #2010
-
- 11 Oct, 2016 2 commits
-
-
Martin Blix Grydeland authored
This test wasn't working as it was supposed to, and would cause the forward links graph building of log transactions to fail. The fail was soft, as the reverse mapping still succeeded creating the right mapping. Depending on when the local thread log buffer was flushed, the problem would show as spurious "duplicate link" log records to be inserted. Fixes: #1830
-
Federico G. Schwindt authored
Fixes #2017.
-
- 14 Sep, 2016 4 commits
-
-
Pål Hermunn Johansen authored
-
Arianna Aondio authored
-
Dridi Boukelmoune authored
-
Pål Hermunn Johansen authored
-
- 13 Sep, 2016 2 commits
-
-
Dridi Boukelmoune authored
With a bit of documentation to explain how to use the two new macros. Closes #2054
-
Dridi Boukelmoune authored
-