[Date Prev][Date Next]
Inconsistent syncrepl behaviour with glue records (ITS#3133)
Full_Name: Luke Howard
Submission from: (NULL) (184.108.40.206)
I am using OpenLDAP 2.2.10 with the patch in ITS#3131.
The master DSA has three databases, each immediately subordinate to the next.
The relevant sections of the configuration file on the master follow:
The replica configuration is similar, in that there are three databases (each
for shadowing the corresponding one on the master) and a default search base and
the DNS SRV backend are both enabled. The relevant sections from the replica
configuration file follow:
The above stanza is repeated twice with the suffix and searchbase changed, for
both "CN=B,DC=foo,DC=bar" and "DC=foo,DC=bar".
Now, to explain the problem:
After provisioning the replica, sometimes the entry at "DC=foo,DC=bar" is synced
correctly from the master, and at other times a glue record is stored. I suspect
that this is a race condition dependent on which database finishes syncing
first. Because the entry at "DC=foo,DC=bar" on the master contains useful
information on which our application depends, the glue record breaks our
application when it uses a replica. As it happens I can duplicate this problem
on one replica DSA, running on Fedora Core 1 under VMware, but not another,
running on SuSE 9.0 on real hardware. However, I have seen the problem manifest
on the latter system in the past.
The glue record appears as follows (DN has been changed for privacy):
# slapcat -n 3
whereas it should really be an instance of object class "domain".