This is the standard RHEL 5.2 build:
openldap-2.3.27-8.el5_1.3
It looks like this RPM doesn't ship with checkpointing enabled, I'll try
that and see how it fares.
Thanks,
Steve
Quanah Gibson-Mount wrote:
--On June 26, 2008 4:45:44 PM +1000 Steve Smith <[EMAIL PROTECTED]>
wrote:
Hi,
I have directory with a group with ~220,000 users in it. This group is
frequently updated (several times an hour). This appears to be causing
the BDB transaction logs to grow very large; over the course of a day
they grow to about 36GB. These all appear to be active; neither
'slapd_db_archive -d' or DB_LOG_AUTOREMOVE has any effect.
Is there anything that can be done about this or is this an unavoidable
side-effect of the transaction system?
What version of BDB are you using? Have you configured a checkpoint in
slapd.conf? What version of OpenLDAP are you using?
There were some bugs in some versions of BDB and I think some version of
OpenLDAP that failed to properly checkpoint, causing the issue you are
seeing. A properly patched version of BDB and a current release of
OpenLDAP should certainly not have this problem.
--Quanah
--
Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra :: the leader in open source messaging and collaboration
