Hi,
We have a single master with multiple replicas. Our backend is mdb, and we
are on the latest version, 2.6.9. The replication type
is refreshAndPersist. Here is the relevant configuration.
syncrepl rid=141
provider=ldaps://ldap-master.georgetown.edu:636/
type=refreshAndPersist
..
..
keepalive=300:5:5
retry="5 5 300 +"
This is now happening at regular intervals. When a consumer replication
gets stuck, only a service restart seems to restart replication.
ex:
ldap-replica-1:1636
# requesting: contextCSN
contextCSN: 20241212135921.652395Z#000000#000#000000
ldap-replica-1:2636
# requesting: contextCSN
contextCSN: 20241220010002.746041Z#000000#000#000000
You can see the replica on port 1636 CSN is stuck at 20241212135921. Any
thoughts?
Thanks,
--
Suresh Veliveli
Sr. UNIX Systems Engineer
Georgetown University
University Information Services | Security Infrastructure and
Policy-Identity and Collaboration
202-262-6676 (cell) | 202-687-3108 (work)
