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,
--On Friday, December 20, 2024 11:22 AM -0500 Suresh Veliveli Suresh.Veliveli@georgetown.edu wrote:
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.
Need more information on what you mean by "getting stuck". Is it actually attemping to get changes? Do you have sync logging enabled? If so, you could see if that particular consumer is having an issue during replication and returning a non-zero result code as to why it's unable to proceed. Or is it not establishing a replication connection at all? etc.
--Quanah
openldap-technical@openldap.org
-
Quanah Gibson-Mount -
Suresh Veliveli