--On Friday, April 08, 2016 1:12 PM -0400 Frank Swasey
Today at 11:03am, quanah(a)zimbra.com wrote:
> I would continue with the documentation update noting that it is
> recommended to run the syncprov overlay on replicas, so that they manage
> their CSN status based off updated received, rather than syncprov
> broadcasts. It's really the correct way to configure a replica,
> regardless of this bug. ;)
Yeah -- so you keep saying ;) ... Patch attached.
Thanks! As per <http://www.openldap.org/devel/contributing.html>
;, can you
regenerate the patch as a git formatted patch, so it is properly
attributed? Also we will need the IPR statement as noted in
> I definitely wouldn't revert anything related to ITS8281,
given that it
> was fixing some serious issues, whereas this issue, while annoying,
> doesn't actually cause harm, and has a workaround that lines up with
> best practices anyway.
No, I was not saying that 8281 should be removed - just that I have built
without the 8281 patch and the "problem" does not happen in that case.
Since I think we both agree that, strictly speaking, syncprov should not
be required on a consumer only configuration; syncrepl probably needs to
be updated to calculate the CSN if it is not present in the response
(that's really all that is being added by having syncprov between
syncrepl and the database - right?). I'm not familiar with the code, so
I don't know how difficult that would be.
Right, Howard's aware of the issue and will be looking into what's
necessary to fix it. ;)
Zimbra :: the leader in open source messaging and collaboration
A division of Synacor, Inc