nginx cache - could not allocate node in cache keys zone

[CJ Ess]

I will try that now - but shouldn't it be evicting a key if it can't fit a
new one?


On Thu, Mar 10, 2016 at 2:38 PM, Richard Stanway <r1ch+nginx at teamliquid.net>
wrote:

> At a guess I would say your key zone is full. Try increasing the size of
> it.
>
> On Thu, Mar 10, 2016 at 8:07 PM, CJ Ess <zxcvbn4038 at gmail.com> wrote:
>
>> This is nginx/1.9.0 BTW
>>
>>
>> On Thu, Mar 10, 2016 at 2:06 PM, CJ Ess <zxcvbn4038 at gmail.com> wrote:
>>
>>> Same condition on two more of the servers in the same pool. Reload
>>> doesn't resolve the issue, but restart does. No limit being hit on disk
>>> space, inodes, open files, or memory.
>>>
>>>
>>> On Thu, Mar 10, 2016 at 12:12 PM, CJ Ess <zxcvbn4038 at gmail.com> wrote:
>>>
>>>> I have four servers in a pool running nginx with proxy_cache. One of
>>>> the nodes started spewing "could not allocate node in cache keys zone"
>>>> errors for every request (which gave 500 status). I did a restart and it
>>>> started working again.
>>>>
>>>> What conditions cause that error in general?
>>>>
>>>> If it happens again is there anything I can do to try and determine the
>>>> root cause?
>>>>
>>>>
>>>
>>
>> _______________________________________________
>> nginx mailing list
>> nginx at nginx.org
>> http://mailman.nginx.org/mailman/listinfo/nginx
>>
>
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20160310/edaee320/attachment.html>