Proxy_cache fills harddrive despite max_size being set

Server NGINX
1

Hello.

In Nginx 0.8.38 (and later; on amd64) I’ve set this:
proxy_cache_path /var/tmp/nginx/cache levels=1:2
keys_zone=my-cache:10m inactive=8h max_size=100m;

Using that cache Nginx fills my harddrive with its cache, ignoring
max_size.

Did somebody else observed that behaviour? Or, did I something wrong?

–
Thanks für your help in advance!
Mark

2

On Wed, Jun 02, 2010 at 08:11:53PM +0200, W-Mark K. wrote:

In Nginx 0.8.38 (and later; on amd64) I’ve set this:
proxy_cache_path /var/tmp/nginx/cache levels=1:2
keys_zone=my-cache:10m inactive=8h max_size=100m;

Using that cache Nginx fills my harddrive with its cache, ignoring max_size.

Did somebody else observed that behaviour? Or, did I something wrong?

What does “du -kcd1 /var/tmp/nginx/cache” show ?

–
Igor S.
http://sysoev.ru/en/

3

Why has this problem not be addressed?

+1bump

Happening to me to, 33M folder in cache when I set to 10M

Posted at Nginx Forum:

4

I’m seeing something similar. du -sb returns 1411480500 bytes, even
though I have specified 1024 MB as max size.

nginx 0.7.62 on ubuntu 9.10 server.

Here is my proxy_cache config:
proxy_cache_path /var/spool/nginx_proxy_cache
levels=1:2
keys_zone=zone1:10m
inactive=7d
max_size=1024m;

Any ideas? Is it the inactive period of 7d that controls when the
cache manager process runs or something?

–
RPM

5

2010/6/2 Igor S. [email protected]:

What does “du -kcd1 /var/tmp/nginx/cache” show ?

du -kc --max-depth=1 /var/tmp/nginx/cache

32459364 /var/tmp/nginx/cache/0
32459368 /var/tmp/nginx/cache
32459368 total

My ‘du’ doesn’t feature parameters “d1”, I hope --max-depth is the same.

Additionally I’ve notice that there are several files larger than
100MB in “cache/0/00”. Given their content, their first lines are most
probably from the upstream - which is fine - but should neither get
cached at all given max_size nor should the garbage (lots of ^@
following the first kilobytes) be there.

–
Mark K.