sync_client behaviour improvement planning

[Sebastian Hagedorn]

Hi,

we're only getting started with replication, so I can't contribute any 
useful comments, but your post raised two questions for me:

This only affects the "new", post-3.0 replication protocol, right? We're 
planning a migration from 2.4 to 3.0 using replication, and I'd like to be 
aware of all potential issues we might encounter.

> Hey - here's me posting something to the public list instead of internal
> FastMail slack.  We've been really bad at making our random ruminations
> public, sorry.
> Tomorrow (Tues 27th) 2pm Melbourne time, I'm going to be meeting with
> ellie and maybe Partha in the Melbourne office with a whiteboard and a
> screen to flesh out some ideas for things we can do to fix some of the
> issues that came up after a recent machine failure event at FastMail.

<snip>

> b) there are over 1000 mailboxes, and the log file got deduplicated and
>    then run in sets, and we had this:
> sync_log MAILBOX Z
> sync_log MAILBOX B
>
> (for a rename of Z to B)

Where and when does deduplication happen?
--
Sebastian Hagedorn - Weyertal 121, Zimmer 2.02
Regionales Rechenzentrum (RRZK)
Universität zu Köln / Cologne University - Tel. +49-221-470-89578
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 262 bytes
Desc: not available
URL: <http://lists.andrew.cmu.edu/pipermail/cyrus-devel/attachments/20180226/10e64060/attachment.sig>