Reuben Farrelly <reuben-dovecot at reub.net> wrote:> Checking in - this is still an issue with 2.3-master as of today (2.3.devel (3a6537d59)).That doesn't sound good, because I did hope that someone has been working on this issue ...> I haven't been able to narrow the problem down to a specific commit. The best I have been able to get to is that this commit is relatively good (not perfect but good enough): > > d9a1a7cbec19f4c6a47add47688351f8c3a0e372 (from Feb 19, 2018) > > whereas this commit: > > 6418419ec282c887b67469dbe3f541fc4873f7f0 (From Mar 12, 2018) > > is pretty bad. Somewhere in between some commit has caused the problem (which may have been introduced earlier) to get much worse.Thanks for the info.> There seem to be a handful of us with broken systems who are prepared to assist in debugging this and put in our own time to patch, test and get to the bottom of it, but it is starting to look like we're basically on our own.I wonder if there is anyone running a 2.3 master-master replication scheme *without* running into this issue? Please let us know: yes, 2.3 master-master replication does run as rock-stable as in 2.2. Anyone? I would love to get some feedback from the developers regarding: #) are commercial customers of yours running 2.3 master-master replication without those issues reported in this thread? #) do you get reports about these issues outside this ML as well? #) and ...> What sort of debugging, short of bisecting 100+ patches between the commits above, can we do to progress this?? what kind of debugging do you suggest? Regards, Michael
> On 31 May 2018, at 17:52, Michael Grimm <trashcan at ellael.org> wrote: > > Reuben Farrelly <reuben-dovecot at reub.net> wrote: > >> Checking in - this is still an issue with 2.3-master as of today (2.3.devel (3a6537d59)). > > That doesn't sound good, because I did hope that someone has been working on this issue ... > >> I haven't been able to narrow the problem down to a specific commit. The best I have been able to get to is that this commit is relatively good (not perfect but good enough): >> >> d9a1a7cbec19f4c6a47add47688351f8c3a0e372 (from Feb 19, 2018) >> >> whereas this commit: >> >> 6418419ec282c887b67469dbe3f541fc4873f7f0 (From Mar 12, 2018) >> >> is pretty bad. Somewhere in between some commit has caused the problem (which may have been introduced earlier) to get much worse. > > Thanks for the info. > >> There seem to be a handful of us with broken systems who are prepared to assist in debugging this and put in our own time to patch, test and get to the bottom of it, but it is starting to look like we're basically on our own. > > I wonder if there is anyone running a 2.3 master-master replication scheme *without* running into this issue? Please let us know: yes, 2.3 master-master replication does run as rock-stable as in 2.2. > > Anyone? > > I would love to get some feedback from the developers regarding: > > #) are commercial customers of yours running 2.3 master-master replication without those issues reported in this thread? > #) do you get reports about these issues outside this ML as well? > #) and ... > >> What sort of debugging, short of bisecting 100+ patches between the commits above, can we do to progress this? > > ? what kind of debugging do you suggest?Aki sent me over some patches recently and I have build a custom package for it for FreeBSD. It?s in my pkg repo which I can forward you if you want it. You need to add some lines to the logging thing and then trace those and collaborate with the dovecot community/developers. I did not have yet found the time to actively persue this due to other things on my head. Sorry for that. I hope to do this ?soon? but I dont want to pin myself to a commitment that I might not be able to make :) Cheers Remko> > Regards, > Michael-------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20180531/4945c646/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: Message signed with OpenPGP URL: <https://dovecot.org/pipermail/dovecot/attachments/20180531/4945c646/attachment.sig>
On 31. May 2018, at 18:09, Remko Lodder <remko at FreeBSD.org> wrote:>> On 31 May 2018, at 17:52, Michael Grimm <trashcan at ellael.org> wrote:>> I would love to get some feedback from the developers regarding: >> >> #) are commercial customers of yours running 2.3 master-master replication without those issues reported in this thread? >> #) do you get reports about these issues outside this ML as well? >> #) and ... >> >>> What sort of debugging, short of bisecting 100+ patches between the commits above, can we do to progress this? >> >> ? what kind of debugging do you suggest? > > Aki sent me over some patches recently and I have build a custom package for it for FreeBSD. It?s in my pkg repo which I can forward you if you want it.Great news. I'd love to test it, thus, could you forward it to me? Thanks.> You need to add some lines to the logging thing and then trace those and collaborate with the dovecot community/developers.And, please let me know, which config is needed for those logging lines as well.> I did not have yet found the time to actively persue this due to other things on my head. Sorry for that. I hope to do this ?soon? but I dont want to pin myself to a commitment that I might not be able to make :)Well, I will give it a try. But: more testers might see more in those logging lines ;-) Regards, Michael