Hello!
On Tue, Apr 09, 2013 at 05:24:12PM -0400, gwinans wrote:
> So, I've run without this third party cache purge module since I mentioned a
> custom build.
>
> The server is still chewing through disk space and IO remains pegged to the
> wall (mix of the cache loader and new cache items). The
So, I've run without this third party cache purge module since I mentioned a
custom build.
The server is still chewing through disk space and IO remains pegged to the
wall (mix of the cache loader and new cache items). The cache loader seems
unable to keep up -- I've never seen it actually delete
Maxim Dounin Wrote:
---
> Hello!
** snip**
> (On the other hand, it may iterfere with normal cache operations
> and may cause problems you observe, much like any other 3rd party
> module. That's why we usually ask people to reproduce the issu
Hello!
On Mon, Apr 08, 2013 at 01:16:34PM -0400, gwinans wrote:
> Maxim Dounin Wrote:
> ---
> > Hello!
> >
>
> ** snip**
>
> > Have you tried without the cache purge module compiled in?
> >
> > --
> > Maxim Dounin
>
> I have not -- this is
Maxim Dounin Wrote:
---
> Hello!
>
** snip**
> Have you tried without the cache purge module compiled in?
>
> --
> Maxim Dounin
I have not -- this is actually an RPM-build from the Atomic Repo. Wouldn't
removing said purge module disable the
Hello!
On Mon, Apr 08, 2013 at 12:28:46PM -0400, gwinans wrote:
> The cache manager process is, indeed, running. I even did a brief strace on
> it to be sure it was actually working. There is nothing in the logs that
> indicates an issue. In fact, the only thing in the logs is expected http
> req
The cache manager process is, indeed, running. I even did a brief strace on
it to be sure it was actually working. There is nothing in the logs that
indicates an issue. In fact, the only thing in the logs is expected http
requests.
Output of nginx -V:
[root@nginx01-dpl ~]# nginx -V
nginx version:
Hello!
On Mon, Apr 08, 2013 at 11:46:55AM -0400, gwinans wrote:
> Hi folks,
>
> We setup some nginx instances a few months ago in order to serve up/cache
> video content. Recently, we've noticed that there is *severe* cache overrun
> -- on the order of 1TB + per cache directory.
>
> It seems li
Hi folks,
We setup some nginx instances a few months ago in order to serve up/cache
video content. Recently, we've noticed that there is *severe* cache overrun
-- on the order of 1TB + per cache directory.
It seems like proxy_cache_path is entirely ignoring the max_size value
specified in the con
