-----Original Message----- From: Howard Chu [mailto:hyc@symas.com] Sent: Tuesday, July 8, 2014 12:08 PM To: Aaron Bennett; openldap-technical@openldap.org Subject: Re: syncrepl_del_nonpresent leading to directory implosion
You have a bad misconfig in your BDB, you need to configure a larger lock table.
and the syncrepl code probably needs to be fixed to quit if the backend returns an LDAP_OTHER error code like this. Please submit an ITS for this.
Thank you -- I will submit an ITS once the dust has cleared.
I adjusted our lock table significantly upwards. However, since then, I'm seeing extreme replication delays in just one direction. I'm not sure if there's an issue with BDB or if I did something else wrong. Here's the chain of events:
Two boxes are called animal and zoot.
1. DB_CONFIG looks like this on both boxes: set_cachesize 0 524288000 1 set_lg_regionmax 262144 set_lg_bsize 2097152 set_flags DB_LOG_AUTOREMOVE set_lk_max_lockers 9000 set_lk_max_locks 9000 set_lk_max_objects 9000 set_lk_partitions 900
2. To make sure I got a clean database, during a maintenance window I stopped slapd on both machines, deleted /var/lib/ldap/* , and reloaded an ldif on animal with this command: sudo -u ldap /usr/local/sbin/slapadd -S 1 -w -l /tmp/animal-now.ldif
3. Then I started slapd and watched zoot had pulled the replica over. Everything seemed kosher -- replication from animal -> zoot is nearly instant as expected, but zoot -> animal is very slow -- like, 15-30 second and often longer then 60, for one very trivial change.
Any ideas what's wrong? If you'd like I can send syncrepl logs or db_stat output.
Thanks for your time,
Aaron Bennett
---- Manager of Systems Administration Clark University ITS