From: Howard Chu Date: Wed, 22 Aug 2012 03:56:41 +0000 (-0700) Subject: Delta-sync Mirror/MMR is now supported X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=e30981838c15a62cf45ebe6d39cdd2b377eadee6;p=openldap Delta-sync Mirror/MMR is now supported --- diff --git a/doc/guide/admin/replication.sdf b/doc/guide/admin/replication.sdf index adcf276cd8..4a499d655d 100644 --- a/doc/guide/admin/replication.sdf +++ b/doc/guide/admin/replication.sdf @@ -426,7 +426,6 @@ is needed to manage which provider is currently active - If backing up the Berkeley database itself and periodically backing up the transaction log files, then the same member of the mirror pair needs to be used to collect logfiles until the next database backup is taken -* Delta-Syncrepl is not yet supported For configuration, please see the {{SECT:MirrorMode}} section below @@ -867,8 +866,6 @@ H4: Mirror Node Configuration The first step is to configure the syncrepl provider the same as in the {{SECT:Set up the provider slapd}} section. -Note: Delta-syncrepl is not yet supported with MirrorMode. - Here's a specific cut down example using {{SECT:LDAP Sync Replication}} in {{refreshAndPersist}} mode: diff --git a/doc/guide/admin/tuning.sdf b/doc/guide/admin/tuning.sdf index 39fc6a4b5d..0890c3b13f 100644 --- a/doc/guide/admin/tuning.sdf +++ b/doc/guide/admin/tuning.sdf @@ -324,7 +324,7 @@ it is generally recommended to be 3x"cachesize". H2: {{slapd}}(8) Threads -{{slapd}}(8) can process requests via a configurable number of threads, which +{{slapd}}(8) can process requests via a configurable number of threads, which in turn affects the in/out rate of connections. This value should generally be a function of the number of "real" cores on