[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Consumer bdb log explosion

To: Mark.Hendricks@humboldt.edu
Subject: Re: Consumer bdb log explosion
From: Aaron Richton <richton@nbcs.rutgers.edu>
Date: Tue, 4 May 2010 16:37:54 -0400 (EDT)
Cc: Buchan Milne <bgmilne@staff.telkomsa.net>, openldap-software@openldap.org
In-reply-to: <232830342.5407641272991710791.JavaMail.root@zimbra.humboldt.edu>
References: <232830342.5407641272991710791.JavaMail.root@zimbra.humboldt.edu>
User-agent: Alpine 2.00 (SOC 1167 2008-08-23)

On Tue, 4 May 2010, Mark.Hendricks@humboldt.edu wrote:

We are running slapd 2.3.43 (Using bdb db4-4.3.29-10.el5) with one provider and two consumers and syncrpl (kerberos/SASL based).
Occasionally when heavy changes to the provider are made, the consumer bdb logs go crazy and fill up the bdb volume.

Remove unnecessary log files prior to volume fill, hopefully inconjunction with a sane backup procedure (I don't know whatldap-hot-backup is, but hopefully it eventually calls slapcat(8) and thatoutput gets put somewhere safe). I assume "10MB file per second" refers totransaction log file size, which sounds like sufficient granularity toremove in a timely fashion in most installations.


http://www.openldap.org/faq/data/cache/738.html

References:
- Consumer bdb log explosion
  - From: Mark.Hendricks@humboldt.edu

Prev by Date: Re: Consumer bdb log explosion
Next by Date: Re: Consumer bdb log explosion
Index(es):
- Chronological
- Thread