similar to: IMAP hibernate and scalability in general

We've been using hibernate for about half a year with no ill effects. There were various logged errors in earlier versions of dovecot, but even with those, we never heard a reported customer-side error (almost always when transitioning from hibernate back to regular imap; in the case of those errors, presumably the mail client just reconnected silently). For no particular reason besides

On 06.04.2017 06:15, Christian Balzer wrote: > Hello, > > as some may remember, we're running very dense IMAP cluster here, in > excess of 50k IMAP sessions per node (current record holder is 68k, design > is for 200k+). > > The first issue we ran into was that the dovecot master process (which is > single thread and thus a bottleneck) was approaching 100% CPU usage

Hello, On Wed, 5 Apr 2017 23:45:33 -0700 Mark Moseley wrote: > We've been using hibernate for about half a year with no ill effects. There > were various logged errors in earlier versions of dovecot, but even with > those, we never heard a reported customer-side error (almost always when > transitioning from hibernate back to regular imap; in the case of those > errors,

Hello, Just to follow up on this, we've hit over 16k (default client limit here) hibernated sessions: --- dovecot 119157 0.1 0.0 63404 56140 ? S Apr01 62:05 dovecot/imap-hibernate [11291 connections] dovecot 877825 0.2 0.0 28512 21224 ? S Apr23 1:34 dovecot/imap-hibernate [5420 connections] --- No issues other than the minor bug I reported, CPU usage is

Hello, Dovecot 2.2.27 (Debian Jessie backports). When issuing a "doveadm kick" for a specific user I was greeted by: --- "warning: other connections would also be kicked from following users:" --- and a list of 22odd thousand users. As it turns out, kick wants to smack the hibernation proces(ses) that have hibernated sessions for this user, obviously the wrong approach here.

On 6 Apr 2017, at 21.14, Mark Moseley <moseleymark at gmail.com> wrote: > >> >> imap-hibernate processes are similar to imap-login processes in that they >> should be able to handle thousands or even tens of thousands of connections >> per process. >> > > TL;DR: In a director/proxy setup, what's a good client_limit for >

On 6 Apr 2017, at 9.56, Christian Balzer <chibi at gol.com> wrote: > >> For no particular reason besides wanting to start conservatively, we've got >> client_limit set to 50 on the hibernate procs (with 1100 total hibernated >> connections on the box I'm looking at). At only a little over a meg each, >> I'm fine with those extra processes. >>

On 24 Apr 2017, at 4.04, Christian Balzer <chibi at gol.com> wrote: > > > Hello, > > Just to follow up on this, we've hit over 16k (default client limit here) > hibernated sessions: > --- > dovecot 119157 0.1 0.0 63404 56140 ? S Apr01 62:05 dovecot/imap-hibernate [11291 connections] > dovecot 877825 0.2 0.0 28512 21224 ? S

On 24 Apr 2017, at 15.41, Timo Sirainen <tss at iki.fi> wrote: > > On 24 Apr 2017, at 4.04, Christian Balzer <chibi at gol.com <mailto:chibi at gol.com>> wrote: >> >> >> Hello, >> >> Just to follow up on this, we've hit over 16k (default client limit here) >> hibernated sessions: >> --- >> dovecot 119157 0.1 0.0

* Timo Sirainen <tss at iki.fi> 2015.08.25 22:21: > There's no good default setting here. It depends on your userdb settings and/or mail_uid setting. So for example if your imap processes are running as vmail user, you should set service imap-hibernate { unix_listener imap-hibernate { user = vmail } }. Then again if you are using system users (or otherwise multiple UIDs) it gets more

Hi everyone, I'm running dovecot with quite a lot of users and lots of active imap connections (like 20'000). I'm using different user IDs for users, so I need to have imap {service_count=1} - i.e. I have a lots of imap processes running. Everything works fine, until I reload dovecot configuration. When that happen, every client is forced to relogin in the same time and that

* Timo Sirainen <tss at iki.fi> 2015.08.25 17:28: > >> ==> /var/log/dovecot/dovecot.log <== > >> Aug 25 09:42:07 nihlus dovecot: imap(tlx at leuxner.net): Error: net_connect_unix(/var/run/dovecot/imap-hibernate) failed: Permission denied > >> Aug 25 09:42:07 nihlus dovecot: imap(tlx at leuxner.net): Error: Couldn't hibernate imap client: Couldn't

After setting imap_hibernate_timeout to 60s, I could not find any hibernated connections after a few hours. I tested hibernation and made an observation: IDLE'd imap sessions only hibernate if they don't have a mailbox SELECT'd, otherwise they never hibernate. Is this the way it's supposed to work? Joseph Tam <jtam.home at gmail.com>

On Thu, Apr 6, 2017 at 3:10 AM, Timo Sirainen <tss at iki.fi> wrote: > On 6 Apr 2017, at 9.56, Christian Balzer <chibi at gol.com> wrote: > > > >> For no particular reason besides wanting to start conservatively, we've > got > >> client_limit set to 50 on the hibernate procs (with 1100 total > hibernated > >> connections on the box I'm

http://hg.dovecot.org/dovecot-2.2/rev/64c73e6bd397 Today I finally committed the "imap-hibernate" feature that I first started developing about a year ago (and had been thinking about for several years before that). The main purpose here is to reduce the number of imap processes and the amount of memory they use by moving IDLEing connections into imap-hibernate processes where they are

Hi, I cannot have suspend and hibernate working on a Samsung NC10 (netbook) running CentOS 5.4 i386. When I try suspending/hibernating the screen becomes black (with a few logs, like "shrinking memory" for hibernate) and then the computer hangs and I have to force a shutdown with the power button. This wiki page seems to say that it should work out of the box:

Hello, this is on Debian Jessie box, dovecot 2.2.27 from backports, imap-hibernate obviously enabled. I've been seeing a few of these since starting this cluster (see previous mail), they all follow the same pattern, a user who accesses their mailbox with both POP3 and IMAP deletes mails with POP3 and the IMAP (imap-hibernate really) is getting confused and upset about this: --- Apr 6

Hello, On Thu, 6 Apr 2017 09:24:23 +0300 Aki Tuomi wrote: > On 06.04.2017 07:02, Christian Balzer wrote: > > > > Hello, > > > > this is on Debian Jessie box, dovecot 2.2.27 from backports, > > imap-hibernate obviously enabled. > > > > I've been seeing a few of these since starting this cluster (see previous > > mail), they all follow the

Hello, On Thu, 6 Apr 2017 20:04:38 +0900 Christian Balzer wrote: > Hello Aki, Timo, > > according to git this fix should be in 2.2.27, which I'm running, so I > guess this isn't it or something else is missing. > See: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859700 > Any update on this? Christian > Regards, > > Christian > > On Thu, 6

* Teemu Huovila <teemu.huovila at dovecot.fi> 2015.08.27 13:58: > Did you specify a value other than zero for 'imap_hibernate_timeout'? Yes I did: $ doveconf imap_hibernate_timeout imap_hibernate_timeout = 1 mins I sometimes see one imap-hibernate process (only one), but several imap processes active which should be idling... -------------- next part -------------- A non-text