Re: sync_log_chain - is it always needed?
On 2020-04-29 03:39, ellie timoney wrote: On Wed, Apr 29, 2020, at 1:12 AM, Olaf Frączyk wrote: I was wondering why do we need to use this option on middle servers in replication chain? Hope this helps, Yes it helped. Thank you. As the replication uses its own protocol even over IMAP connection it makes sense. However why the sync_log_chain could be not always active? As the server catches all changes from LMTP, IMAP, POP anyway, why to use a special option for the synchronization protocol? Why to treat replication changes differently from LMTP/IMAP? If we want replication - we want to catch all changes - regardless of the source, if we don't do replication - we don't need to catch any changes. ellie 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 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
Re: Replication failed 3.0.5 -> 3.0.13
W dniu 22.04.2020 o 10:19, Olaf Frączyk pisze: > On 2020-04-22 09:16, Andrzej Kwiatkowski wrote: >> W dniu 20.04.2020 o 16:11, Olaf Frączyk pisze: >>> Hi, >>> >>> I'm running 3.0.5. >>> >>> I want to migrate to a new machine. I set up cyrus-imapd 3.0.13. >>> >>> The replication started but it didn't transfer all mails. >>> >>> The store isn't big 44GB, transferred was about 24 GB. >>> >>> In the logs I see: >>> >> Olaf, >> >> Do you install 3.0.13 on vm or bare-metal ? >> >> Regards >> AK > > I have it installed in VM - CentOS 7, now 8. This setup worked OK for > many years. But I have only a few users, just with big mailboxes. > > On SAS drives it works fine. The only longlock I saw was during the > replication - I suppose transferring 20.000 big messages at once per > mailbox could cause it. But in normal usage I don't see it. > > The cause of my problem was my ignorance regarding how rolling > replication works in cyrus. It works OK now :) > > Regards, > > Olaf > Ok. I was asking because of problem with low entropy on VM-s causing performance issues with big installations. I've also noticed that replication documentation is a bit tricky, and not every procedure/case is well documented. Regards AK 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
Re: Replication failed 3.0.5 -> 3.0.13
On 2020-04-29 16:47, Andrzej Kwiatkowski wrote: Ok. I was asking because of problem with low entropy on VM-s causing performance issues with big installations. I didn't have this issue, however as I said, my installation is really small. If I needed more entropy I would think of using a hardware entropy generator. Eg. on a PCI-e card. They aren't super cheap but also not too expensive. I think someone with good cryptography knowledge could help you with this topic. I suppose the storage I/O can be a bigger issue here. I've also noticed that replication documentation is a bit tricky, and not every procedure/case is well documented. Yes, me too ;) But if you hit a bigger problem, you have this list :) I tried on a copy without active users to be safe. Regards AK 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
Mailbox rename and Cyrus murder
Hi, Sometimes, we need to redistribute mailboxes between different Cyrus partitions in the same server. We do it by blocking previously any kind of accesses to the mailbox and after stopping any kind of active connection to that mailbox. I was wondering, if this exactly, is really needed because it’s really something that could cause problems to the mailbox (we do it this way always, as a procedure for avoiding problems, but is it really needed??). I’m in the process of automating this kind of operation, but reading some info before writing code, I have seen that Cyrus murder allows “live” mailbox migration… perhaps is this another option for avoid doing mailbox rename operations for moving a mailbox to a different partition?. I have read too (perhaps have not understand properly), that a Cyrus Murder can redirect requests to another mailbox server, in case one of them fails?. Is it like a automated way of changing master/slave roles?. How is your experience with murders?. Do they allow this what I have asked?. If they do have you ever seen any kind of issue with it?, Cheers, 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
