Replica mailboxes changing partitions during delayed deletes

Bron Gondwana brong at fastmail.fm
Mon Nov 23 16:10:54 EST 2009


On Mon, Nov 23, 2009 at 02:59:47PM -0600, Paul Engle wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> All,
> 
> We've just upgraded our first replicated pair of cyrus servers 
> to 2.3.15, and I'm seeing what I consider odd behavior on the 
> replica of the pair.
> 
> A brief rundown of our configuration:
> 
> Both servers running RHEL5, cyrus-imapd-2.3.15
> Three partitions on each server: cyrus1a (default), cyrus1b, 
> cyrus1c
> Delayed delete is turned on for both the master & the replica
> 
> This morning, when I performed a user cleanup and deleted a 
> batch of user INBOXes, I noticed the sync_server process was 
> going dog-slow and the replication log was backing up on the 
> master.
> 
> It turns out that, on the replica, when a mailbox gets deleted, 
> the DELETED mailbox is being put on the default partition 
> rather than the partition it started on. As a result, anything 
> not native to the default partition is having to get copied 
> from one filesystem to the other, causing the replication to 
> slow down considerably. On the master server, the DELETED 
> mailbox is put on the same partition it started on.
> 
> Is this desired behavior? I wouldn't think so, and at this 
> point I'm going to have to turn off delayed deletes on our 
> replica target so that the sync_server stops bogging down.

Oh man - that's almost certainly a bug!  We don't notice it
at FastMail because we only have one partition per server.
I'll check it out.

Bron.


More information about the Info-cyrus mailing list