Inner workings of nginx cache manager

[Stefan Safar]

Hi there,

I'd like to know a little bit more about the inner workings of the cache
manager. I looked through the code, and if I understand it correctly, when
it runs out of disk space specified by max_size, it tries to run the cache
manager, which looks at a queue of last-accessed URLs and tries to remove
the least used URL from the queue and from the disk.

My question is, whether the queue is somehow persisted on disk, or I
misunderstood something? What I'm trying to know is what happens when an
nginx instance runs out of disk space and it's restarted - how does nginx
know what it should or shouldn't delete? I don't think I saw any code that
would scan through the disk and that would be a rather slow way to deal
with this.

Thanks,

Stefan Safar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20181129/d6d9b995/attachment.html>