Welcome! Log In Create A New Profile

Advanced

Re: Can the cacheloader process stay alive and keep rebuilding or updating the cache metadata?

September 29, 2017 04:56PM
It would help in a use-case when there are 2 NGINX processes, both working with the same cache directory.

NGINX-A runs with a proxy-cache-path /disk1/cache with zone name "cacheA".

NGINX-B runs with the same proxy-cache-path /disk1/cache with zone name "cacheB".

When NGINX-B adds content to the cache (say for URL test/a.html), the file gets added to cache as /disk/cache1/test/a.html (again, avoiding md5 for simplicity).

I think it may be nice if a subsequent request for this URL to NGINX-A would result in a hit, as the file is available in the disk. However, today it does not result in a HIT, as the in-memory metadata is missing for NGINX-A for this URL. So, it would fetch from origin and add it again to cache, and update its in-memory metadata.

Otherwise, a restart of NGINX-A would build up the cache metadata for files found in the cache directory.

Thanks
Rajesh
Subject Author Posted

Can the cacheloader process stay alive and keep rebuilding or updating the cache metadata?

rnmx18 September 29, 2017 04:27PM

Re: Can the cacheloader process stay alive and keep rebuilding or updating the cache metadata?

Lucas Rolff September 29, 2017 04:38PM

Re: Can the cacheloader process stay alive and keep rebuilding or updating the cache metadata?

rnmx18 September 29, 2017 04:56PM

Re: Can the cacheloader process stay alive and keep rebuilding or updating the cache metadata?

rnmx18 September 29, 2017 05:05PM

Re: Can the cacheloader process stay alive and keep rebuilding or updating the cache metadata?

Lucas Rolff September 29, 2017 05:08PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 69
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready