Cache survived varnish restart?

[CJ Ess]

I didn't think so either but not sure how to explain the lack of disruption
from the restarts.


On Mon, Oct 31, 2016 at 5:21 AM, Guillaume Quintard <
guillaume at varnish-software.com> wrote:

> I don't think that's possible :-) That would be nice though.
>
> --
> Guillaume Quintard
>
> On Thu, Oct 27, 2016 at 8:41 PM, CJ Ess <zxcvbn4038 at gmail.com> wrote:
>
>> I saw something today that I can't explain - I upgraded Varnish 4.1.0 to
>> v4.1.3 by restarting varnishd on a server. I can see that inode of the
>> executable and libraries are right for the updated files in the running
>> varnishd via /proc/<pid>/maps (on Linux), I can see that no other varnishd
>> processes are running. I expected that restarting varnish would cause the
>> cache to be wiped and require some period of warmup, however the hit rate
>> held steady at 98% and I don't know why.
>>
>> I'm very happy to be able to do this, its going to make the rest of my
>> upgrades non-disruptive, but I'd like to be able to explain whats happening
>> behind the scenes. Can anyone tell me how the cache seemed to survive the
>> restart?
>>
>>
>> _______________________________________________
>> varnish-misc mailing list
>> varnish-misc at varnish-cache.org
>> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20161101/d5576f45/attachment.html>