----- Original Message -----
From: "Paul B. Henson" henson@acm.org To: openldap-technical@openldap.org Sent: Wednesday, December 21, 2016 6:56:30 PM Subject: memberOf overlay issues with 2.4.44 + ITS 8432 patch
So far, I've only seem this behavior for group membership removals. Adds don't seem to cause a problem, nor do create/delete of groups or users as far as I can tell.
Any thoughts on what's going on here? It's not causing any failures yes, as removing members multiple times results in the same end state and the multiple replication seems to have a fairly low upper bound. But it would be nice to fix it :).
Looks like a bug with the memberOf overlay when it is instantiated in a delta-syncrepl environment, based on this statement from the memberOf man page:
The memberof overlay may be used with any backend that provides full read-write functionality, but it is mainly intended for use with local storage backends. The maintenance operations it performs are internal to the server on which the overlay is configured and are never replicated. Replica servers should be configured with their own instances of the memberOf overlay if it is desired to maintain these memberOf attributes on the replicas.
Probably worth adding to ITS#8444.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
On Thu, Dec 22, 2016 at 10:35:55AM -0600, Quanah Gibson-Mount wrote:
Looks like a bug with the memberOf overlay when it is instantiated in a delta-syncrepl environment, based on this statement from the memberOf man page:
This is new behavior as of 2.4.44; I had the exact same memberOf/delta-syncrepl configuration under 2.4.41 and never saw this issue.
Probably worth adding to ITS#8444.
Ok, will do. Although it seems there's been no response to that ticket for six months :(? Anything else I can provide to help debug this? Unfortunately it doesn't seem to be a straight "always happens" bug, I didn't see it all in my dev environment under a test load, it only popped up in production under a full load.
Thanks...
openldap-technical@openldap.org