• Nils Goroll's avatar
    fix probe not started for already warm vcl · d912ffe4
    Nils Goroll authored
    For (real) backends, we used to assign the probe after adding the
    director via VRT_AddDirector(). For an already warm vcl, this lead to
    a VCL_WARM event missed because the event was issued by
    VRT_AddDirector() when the probe did not exist yet.
    
    We fix this by preparing all of the backend before adding the
    director, undoing the work for a failure doing do.
    
    In addition, if adding a backend while the vcl is cold, we need to set
    the initial director state based on the probe configuration after
    adding the director.
    
    We avoid the overhead of the vcl temperature lock because no harm is
    done: If, after the director was added, the temperature goes cold, we
    just run an additional update, and if it goes warm, the update will
    already have happened.
    
    Likely related to https://github.com/nigoroll/libvmod-dynamic/issues/35
    d912ffe4
Name
Last commit
Last update
.github Loading commit data...
bin Loading commit data...
doc Loading commit data...
etc Loading commit data...
include Loading commit data...
lib Loading commit data...
m4 Loading commit data...
man Loading commit data...
tools Loading commit data...
.dir-locals.el Loading commit data...
.gitignore Loading commit data...
.syntastic_c_config Loading commit data...
.travis.yml Loading commit data...
CONTRIBUTING Loading commit data...
ChangeLog Loading commit data...
INSTALL Loading commit data...
LICENSE Loading commit data...
Makefile.am Loading commit data...
README.Packaging Loading commit data...
README.rst Loading commit data...
autogen.des Loading commit data...
autogen.sh Loading commit data...
configure.ac Loading commit data...
flint.lnt Loading commit data...
varnish-legacy.m4 Loading commit data...
varnish.m4 Loading commit data...
varnishapi-uninstalled.pc.in Loading commit data...
varnishapi.pc.in Loading commit data...