Lots of questions:
What are the upstream requests?
Are you logging hits and misses for the cache - what's the hit ratio?
What size are the objects that you are serving?
How many files are there in your cache?
What OS and what hardware are you using? If it's Linux can you show the results
of the f
Dear Folks,
On 19/09/17 11:16 +1000, Nick Urbanik wrote:
On 19/09/17 10:46 +1000, Nick Urbanik wrote:
We have this message repeatedly, despite increasing keys_zone size by
a factor of three to:
proxy_cache_path/srv/mycache levels=1:2 keys_zone=myzone:150m
inactive=15d;
Is it pos
Dear Folks,
On 19/09/17 10:46 +1000, Nick Urbanik wrote:
We have this message repeatedly, despite increasing keys_zone size by
a factor of three to:
proxy_cache_path/srv/mycache levels=1:2 keys_zone=myzone:150m
inactive=15d;
This caused the errors to stop for three or four hours a
Dear Folks,
We have this message repeatedly, despite increasing keys_zone size by
a factor of three to:
proxy_cache_path/srv/mycache levels=1:2 keys_zone=myzone:150m
inactive=15d;
This caused the errors to stop for three or four hours and then back
again.
The cache itself is quite
> It does so - if an allocation of a cache node fails, this will
> trigger a forced expiration of a cache node, and then tries to
> allocate a node again. This is more an emergency mechanism
> though (and not guaranteed to work, as another allocation may
> fail, too), hence alerts are logged i
Hello!
On Wed, Apr 02, 2014 at 07:41:13PM -0400, jakubp wrote:
> > What currently can be used for such a use case is "inactive="
> > parameter of the proxy_cache_path directive (see
> > http://nginx.org/r/proxy_cache_path). It ensures that items not
> > recently requested are removed from the
> What currently can be used for such a use case is "inactive="
> parameter of the proxy_cache_path directive (see
> http://nginx.org/r/proxy_cache_path). It ensures that items not
> recently requested are removed from the cache, including ones
> created with proxy_cache_min_uses. Have you tr
Hello!
On Wed, Apr 02, 2014 at 05:30:55AM -0400, jakubp wrote:
> Hi Maxim
>
> Let me explain the use case.
> I am using cache module to serve very large library. Some files are very
> popular but a ot of them are not popular at all though. To deal with this
> long tail I use proxy_cache_min_uses
Hi Maxim
Let me explain the use case.
I am using cache module to serve very large library. Some files are very
popular but a ot of them are not popular at all though. To deal with this
long tail I use proxy_cache_min_uses to cache only after it was requested
several times. So what I think happens
Hello!
On Mon, Mar 31, 2014 at 08:13:20PM -0400, jakubp wrote:
> Hi
>
> I am struggling with the very same issue at the moment...
>
> If I read the right the code correctly all that nginx cares about is cache
> size, keys zone size is not checked at all (except when more space needs to
> be all
Hi
I am struggling with the very same issue at the moment...
If I read the right the code correctly all that nginx cares about is cache
size, keys zone size is not checked at all (except when more space needs to
be allocated).
ngx_http_file_cache_manager(void *data)
{
//
if (size < cach
> On Wednesday 27 March 2013 16:34:27 praveenkumar Muppala wrote:
> > Hi,
> >
> > We have a nginx1.0.5 version installed in our system. We are getting
> this
> > error continuously in our nginx error log. ngx_slab_alloc() failed:
> no
> > memory in cache
On Wednesday 27 March 2013 16:34:27 praveenkumar Muppala wrote:
> Hi,
>
> We have a nginx1.0.5 version installed in our system. We are getting this
> error continuously in our nginx error log. ngx_slab_alloc() failed: no
> memory in cache keys zone "zone-xyz". I have in
Hi,
We have a nginx1.0.5 version installed in our system. We are getting this
error continuously in our nginx error log. ngx_slab_alloc() failed: no
memory in cache keys zone "zone-xyz". I have increased this value to 20G,
even 30G also still getting the same error. Can you help to fix
14 matches
Mail list logo
