dovecot - Oct 2007 - some mail accesses in dovecot 1.1 stall for a bit (in progress)

I noticed this in an earlier beta and took a note, and I still see it sometimes
in 1.1b4, but it is only occasional so I have not tracked down yet what dovecot
is doing.  Just a FYI for the list incase others see it and to say that its an
issue I tend to track down that I did not see in 1.0, and its been low on my 
list until now.

Sometimes when I login to dovecot and read a message from an imap maildir
folder,
the message contents do not load for at least 10 seconds, sometimes closer to a 
minute, but after that first message loads, the rest seem fine in that mailbox.
The time seems to vary some, usually longer rather than shorter.

On Mon, 2007-10-29 at 17:15 -0400, Adam McDougall wrote:
> Sometimes when I login to dovecot and read a message from an imap maildir
folder,
> the message contents do not load for at least 10 seconds, sometimes closer
to a
> minute, but after that first message loads, the rest seem fine in that
mailbox.
> The time seems to vary some, usually longer rather than shorter.  
Getting a strace from what the imap process is doing at the time would
be useful. It sounds a bit like a stale dotlock, although Dovecot waits
for two minutes for that. http://hg.dovecot.org/dovecot/rev/6dd5df1c1ec9
fixes a stale dotlock overriding issue.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20071102/d7822cf5/attachment-0002.bin>

On Fri, Nov 02, 2007 at 06:04:12PM +0200, Timo Sirainen wrote:

  On Mon, 2007-10-29 at 17:15 -0400, Adam McDougall wrote:
  > Sometimes when I login to dovecot and read a message from an imap maildir
folder,
  > the message contents do not load for at least 10 seconds, sometimes
closer to a
  > minute, but after that first message loads, the rest seem fine in that
mailbox.
  > The time seems to vary some, usually longer rather than shorter.  
  
  Getting a strace from what the imap process is doing at the time would
  be useful. It sounds a bit like a stale dotlock, although Dovecot waits
  for two minutes for that. http://hg.dovecot.org/dovecot/rev/6dd5df1c1ec9
  fixes a stale dotlock overriding issue.
  
Agreed, I've wanted to get a trace since the first time I saw it, but
I've been
using dovecot 1.1 all week and hardly seen it.  Its possible a patch improved it
or there was some other cause, so its just something I'll watch out for and
try
to tackle as soon as it becomes reproducable.  After some further preparation 
this weekend I plan to expand my testing of 1.1 beyond just myself and one
server,
since I've been very happy with the current state of 1.1 this week versus
1.0.