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

Re: How long can a LDAP frontend be down (master and slave) ?

To: Alex Waldus <alex.waldus@cmg.com>
Subject: Re: How long can a LDAP frontend be down (master and slave) ?
From: Alister Winfield <alister.winfield@uk.easynet.net>
Date: 26 Nov 2002 08:52:16 +0000
Cc: openldap-software@OpenLDAP.org
In-reply-to: <11A760648FE3D211BE5200A0C9F2A1940222C8F6@NL-ENS-MAIL01>
References: <11A760648FE3D211BE5200A0C9F2A1940222C8F6@NL-ENS-MAIL01>

On Mon, 2002-11-25 at 15:14, Alex Waldus wrote:
> 
> I have a question about the replication between MASTER and SLAVE ldap
> servers.
> 
> How long can a LDAP Front-end (SLAVE) be down before the slurpd running on
> the backends can not update(sync) it anymore.
> 
> Is it the total free diskspace?

Basically you need enough diskspace + enough memory for slurpd. Slurpd
holds most (possibly all) of the replica log in memory for processing.
If you have only Master -> one slave, then its probably worth just
stopping slurpd and only restarting when the slave is back online.

--
Alister Winfield - Easynet Limited

References:
- How long can a LDAP frontend be down (master and slave) ?
  - From: Alex Waldus <alex.waldus@cmg.com>

Prev by Date: Re: "TLS certificate verification: Error, self signed certificate"
Next by Date: RE: ldap + mysql
Index(es):
- Chronological
- Thread