analyse if this may be problematic, because dovecot index management uses stat quite frequently.
ls/stat on files being extended
If another client is currently extending files in the listed directory, then an ls -l may take an exceptionally long time to complete, as the lister must wait for the writer to flush data in order to do a valid read of the every file’s size. So unless you really need to know the exact size of every file in the directory, just don’t do it!
This would also apply to any application code that was directly issuing stat system calls on files being appended from another node.
analyse if this may be problematic, because dovecot index management uses stat quite frequently.
ls/stat on files being extended
If another client is currently extending files in the listed directory, then an ls -l may take an exceptionally long time to complete, as the lister must wait for the writer to flush data in order to do a valid read of the every file’s size. So unless you really need to know the exact size of every file in the directory, just don’t do it!
This would also apply to any application code that was directly issuing stat system calls on files being appended from another node.
source: http://docs.ceph.com/docs/master/cephfs/app-best-practices/