On 02/14/2018 10:35 AM, Lists Nethead wrote:Quoting Nic Bernstein <nic@xxxxxxxxxxx>: In general, for each consumer of a sync_log, a new log should be defined in `sync_log_channels:`. I use the word "consumer" there intentionally, as the processes which use these logs actually consume them, and leave nothing behind (assuming it all works as expected). So if more than one process tries to eat up the same log, you'll have problems. The overloading of the sync_log framework for purposes beyond replication is new in 3.0, so we're still getting the documentation up to snuff in that regard. However, the documentation already makes this concept clear in that when using more than one replica you need to specify more than one sync_log via the `sync_log_channels:` directive (see https://www.cyrusimap.org/imap/reference/admin/sop/replication.html#channels for details). We obviously do need to produce more generalized documentation for this whole scheme, and I'll be using this discussion as a guide in that regard. sync_log, as the name implies, started life as a way for the "master" server to provide a list of "units" -- either users or mailboxes -- it has touched, so that a replica knows what to request in updates. This is such a useful concept, however, that it is spreading to other subsystems which need to know what might have changed in a potentially large data set (the typical mail store) and so we need to explain this not just in the Replication documentation, but in a more general way. Note also that there is a `sync_log_unsuppressable_channels:` directive, which defaults to "squatter". This is defined as: If you are going to use a name other than "squatter" for your rolling indexing sync_log channel, then you need to update this as well. Cheers, -nic |
begin:vcard fn:Nic Bernstein n:Bernstein;Nic org:Onlight, Inc. adr:Suite 24;;6525 W Bluemound Road;Milwaukee;WI;53213-4073;USA email;internet:nic@xxxxxxxxxxx title:VP Operations tel;work:414-272-4477 x204 tel;cell:414-807-1734 url:http://www.onlight.com/ version:2.1 end:vcard
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
