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

Re: Master replication server reliability

To: openldap-software@OpenLDAP.org
Subject: Re: Master replication server reliability
From: Dieter Kluenter <dieter@dkluenter.de>
Date: Thu, 12 Aug 2004 20:02:28 +0200
In-reply-to: <6991EE283F61E04A957B5368C5765577250121@camail02.ipcfcdom.inphonic.com> (James Courtney's message of "Thu, 12 Aug 2004 12:15:09 -0400")
References: <6991EE283F61E04A957B5368C5765577250121@camail02.ipcfcdom.inphonic.com>
User-agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Rational FORTRAN, linux)

"James Courtney" <Jcourtney@inphonic.com> writes:

> I will try to build/install 2.2 in our dev environment today.  I believe
> I've seen some emails on this list WRT fast loading using slapadd if
> certain transaction parameters are set/disabled somehow in Berkeley DB.
> Is this a practical/safe thing to do for data loading to a new server if
> one re-enables things correctly when done?  Is this a standard practice
> documented somewhere that I could educate myself on further?

Yes it is, man slapadd(8) and
http://www.sleepycat.com/docs/ref/toc.html

add to your DB_CONFIG file the line
set_flags DB_TXN_NOSYNC
and disable this line when running slapd.

-Dieter

-- 
Dieter Klünter | Systemberatung
Tel.: +49.40.64861967
Fax : +49.40.64891521
http://www.avci.de

References:
- RE: Master replication server reliability
  - From: "James Courtney" <Jcourtney@inphonic.com>

Prev by Date: Re: access rules doesn't match
Next by Date: Re: access rules doesn't match
Index(es):
- Chronological
- Thread