[Date Prev][Date Next]
Re: LDAP, bdb, don't want log files for replication
I personally leave logging enabled on my master server and have it
turned off on my replica's -- I have several replicas and use a
loadbalancer to spread the traffic across them, so if one crashes and
burns the extra 5 minutes to get it back up (slapcat the master's db and
slapadd it on the replica) is not a major problem for me.
On 4/18/05 2:07 PM, Armbrust, Daniel C. wrote:
If you are using a 4.2 release of BerkeleyDB, (preferably 4.2.52 + patches) you may disable transaction logging by putting these two lines in your DB_CONFIG file:
You cannot do this with the 4.3 releases of BerkeleyDB.
To me, turning on the logs sounds like madness (but my use case of openldap is quite different from most) because the performance penalty is far to severe, so to each his own.
From: owner-openldap-software@OpenLDAP.org [mailto:owner-openldap-software@OpenLDAP.org] On Behalf Of Adam Tauno Williams
Sent: Monday, April 18, 2005 11:32 AM
Subject: Re: LDAP, bdb, don't want log files for replication
I need a very very fast LDAP server.
I actually use OpenLDAP with bdb, and I notice that most of the time is
taken to write logs for recovery/replication (file log.000000XXXXX).
I don't need this files, and I searched on the web to tune bdb with no
success. I had only found option about cache size, but it's not sufficient.
How can I run an OpenLdap server without generating this files ?
I've collected what performance tuning notes I could find in -
The best approach to me seems to be putting the database and longs on seperate
sets of spindles, that helps allot. Honestly, turning of the logs sounds like
madness to me.
Frank Swasey | http://www.uvm.edu/~fcs
Informtn Tech Profssnl Sr | Always remember: You are UNIQUE,
University of Vermont | just like everyone else.
"I am not young enough to know everything." - Oscar Wilde (1854-1900)