What can lead to a zone memory exhaustion and how Nginx reacts to it?
nginx-forum at nginx.us
Fri Dec 7 21:28:21 UTC 2012
What is a possible scenario for exhausting the memory designated to a
connection zone with limit_conn_zone directive and what are the implication
in this case?
Suppose I have this in my configuration:
limit_conn_zone $binary_remote_addr zone=connzone:1m;
limit_conn connzone 5;
which, according to the documentation, allocates 16000 states for 'connzone'
on a 64-bit server. It also says that "If the storage for a zone is
exhausted, the server will return error 503 (Service Temporarily
Unavailable) to all further requests".
Well, Ok. But what does it mean on practice? When does this happen? Who
receives those 503s? Does it mean that if the number of IPs *somehow*
associated with 'connzone' hits 16000 everyone gets a 503 and it's all over?
How does Nginx decide? The documentation is weirdly vague on this.
So, considering the example config, who would actually get a 503 and under
which circumstances and how would things go from there? Same with request
Posted at Nginx Forum: http://forum.nginx.org/read.php?2,233709,233709#msg-233709
More information about the nginx