max_size is not a strict limit. It's just another watermark for cache
manager to start deleting files.
Also, there might be a difference between du and cache manager used
space estimation
(https://github.com/nginx/nginx/blob/f8a9d528df92c7634088e575e5c3d63a1d4ab8ea/src/os/unix/ngx_files.h#L188)
I can not see any open files once i fire the command on affected servers :
lsof -n /cache | grep deleted
Also my question is why nginx is not limiting use of cache directory to its
max_size , like in this case I have mentioned max_size for cache directory
as 200G but in actual particular cache dire
Hello, omkar_jadhav_20
It might occur that nginx keeps files opened while serving them to slow
clients.
You can try looking for these files with 'lsof -n /cache | grep deleted'.
In a case like this you might want to set a timeout for clients or use
smaller files/chunks.
It looks like nginx c
Hi,
we are running nginx with version 1.10 on redhat 7.2 OS. We have set
max_seize limit for cache of particular application. But we have observed
that cache manager is clearing the space from cache but not at desired speed
. below are few details :
FilesystemType Size Us
