Hi everyone, We have some clusters of varnishd and we're using varnish CLI to trigger failover by setting the "admin health" of a backend to sick.
It works well, until: - we upgrade varnish (occurs a restart) - we change VCL (occurs a reload) - varnishd crashes (notably because of 3rd party VMODs) So, we're trying to find a way of preserving the "admin" states across restart/reload/crashes. We're thinking about reusing vagent2, or creating another intermediate above the Child, but I'm wondering first if this is not better suited in Varnish Core as a basic feature? But then, where? Thanks for your time, -- Jonathan Thomson Reuters ________________________________ This e-mail is for the sole use of the intended recipient and contains information that may be privileged and/or confidential. If you are not an intended recipient, please notify the sender by return e-mail and delete this e-mail and any attachments. Certain required legal entity disclosures can be accessed on our website.<http://site.thomsonreuters.com/site/disclosures/> _______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
