On a train with limited power and internet, but I strongly disagree with
partial repair where some mailboxes don't get synced.
I'm happy with a "failing mailbox gets copied to next sync log file" so long as
it can tell that no mailbox in the log file succeeded and back off rather than
busy spin
This is veering off topic -- as per my original email, I'm talking
specifically about locked replication targets (not corrupted, desynced,
or otherwise broken), and I'm talking specifically about replication to
a backupd (since no other part of Cyrus replication produces a locked
mailbox response).
On Wed, 2016-06-29 at 10:20 -0400, Giles Malet via Cyrus-devel wrote:
> On Wed, 22 Jun 2016 12:25:28 +1000
> ellie timoney via Cyrus-devel wrote:
> D) Don't add the new sync_action_list. If any operation returns
> > IMAP_MAILBOX_LOCKED, just sync_log() that operation and continue, and
> > let th
On Wed, 22 Jun 2016 12:25:28 +1000
ellie timoney via Cyrus-devel wrote:
D) Don't add the new sync_action_list. If any operation returns
> IMAP_MAILBOX_LOCKED, just sync_log() that operation and continue, and
> let the next run deal with it.
I meant to comment on this a while ago, and your lates
> D) Don't add the new sync_action_list. If any operation returns
> IMAP_MAILBOX_LOCKED, just sync_log() that operation and continue, and
> let the next run deal with it.
>
> [...]
>
> I'm inclining towards D at the moment (less code=>less bugs), even
> though it means throwing away most of my e
This might be long, I'm going to front-load a bunch of background
information to provide context to my eventual questions.
I'm talking primarily about sync_client in rolling aka repeat mode,
where it processes a channel's sync log ad infinitum. The one-shot
invocations of sync_client are largely
