I ran nfs3 with dovecot using dotlock and then nlm lock since 2008,
never had an issue, using maildir.
I moved to director arouns 2015, and then to mdbox to fix several
performance issues.
I have moved to nfs4 about 2years ago, but still using director and mdbox.
For me to move without director, would require a user aware load
balancer, as my clients log in from many ip's at the same time.
But I have been thinking of removing nfs, and maybe the directors and
just handling it directly on the nfs servers as the move to mdbox and
everything else is really trimming my requirements.
Quoting pierre.alletru@gmail.com:
Hi Dovecot community,
We're looking at running multiple Dovecot backend servers in
parallel, all using the same shared NFSv4.1 mount to store mailboxes
in the maildir format.We've read in multiple places that running multiple backends with a
shared NFS can result in issues like index files corruption. The
standard solution seems to use the Director feature, or some kind of
IP based proxy/load balancer.But: 1 - The Director feature will be removed in future free versions of
Dovecot
(https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/thread/ILA3C6...). 2 - NFSv4 and above support file locking (flock and fcntl, flock
being emulated using fcntl). 3 - It looks like Dovecot does use file locking, though we're unsure
if it does on everything and in particular on index files.Thus, we are wondering if the need for Director is still relevant
with NFSv4? Shouldn't it work without Director thanks to file
locking? Has anyone tried it? We're thinking that the documentation
and various threads on the subject may be outdated, based on NFSv3
and lower (no file locking).If it doesn't work, anybody knows why? Isn't file locking there
precisely to handle concurrency?Thanks!
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org