20 Sep
2012
20 Sep
'12
10:38 a.m.
On 20/09/12 15:29, Alan DeKok wrote:
Brian Julin wrote:
After collecting some more debug logs, I noticed that this problem was happening too often on requests numbered around 260 to be a coincidence. It turns out this happens after a thread is marked for recycling due to having handled over 128 requests.
Well, set "max_requests_per_server = 0".
There's really no reason to clean up old threads.
Indeed. It's not like it will free up any OS resources - memory or file descriptor leaks are per-process.