Thanks for the input!
Great to know that you got clusters working with at least some version of NFS
without using Director. Were you guys using NLM (Network Lock Manager),
dotlock, or something else, to have file locking capabilities with NFSv3?
The delegation feature of NFSv4 mentioned by Adri
Thanks Tom. Are you refering to a proxy software in particular (e.g. Dovecot
proxy, Nginx, ...)? Do you mean having a single proxy in front of all the
backends?
We'd prefer to avoid that if possible, as that makes the proxy a single point
of failure. But it seems to be the recommended way to de
Hi Dovecot community.
We're seeing a ton of imap-login processes running even when using high
performance mode
(https://doc.dovecot.org/admin_manual/login_processes/#high-performance-mode).
According to the docs:
"process_min_avail should be set to be at least the number of CPU cores in the
s
Well I'm not sure what happened but the issue seems to have resolved itself
somehow:
$ ps aux | grep "dovecot/imap" | wc -l
2168
$ ps aux | grep "dovecot/imap" | grep IDLE | wc -l
56
$ ps aux | grep "imap-hibernate"
syslog863411 0.4 0.0 16660 15296 ?S09:07 1:40
dovecot/imap-
After further testing we realized that it was due to service_count = 100. We
suspect that when the service count is reached, a new process is spawned,
explaining the large number of imap-login processes.
With service_count = 0 we stick with only 4 processes (process_min_avail).
However, we're c
Thank you Joseph and Aki!
You got it right, the issue was indeed with this service_count=100. With
service_count=0 it works as intended (only 4 imap-login processes), though now
we're concerned about possible memory leaks with this config.
What you described Jospeh
(https://www.mail-archive.co
It seems to us that the ideal solution would be that once service_count is
reached, a new process is spawned and the remaining connections are moved to
that new process so that the old one can die quickly. But I suspect that's not
a simple change to do.
__
Awesome, thank you for the information Aki. :) We'll set vsz_limit and keep
service_count = 0, as service_count >= 1 is not an option for us due to the
high memory consumption associated with having many imap-login processes
running.
The new process_shutdown_filter option looks interesting, tho
