mirror/openldap
2
0
Fork 0
mirror of https://git.openldap.org/openldap/openldap.git synced 2025-01-30 13:30:57 +08:00
Code Issues Packages Projects Releases Wiki Activity

syncprov overlay section.

Browse Source
This commit is contained in:
Gavin Henry 2008-11-24 16:09:35 +00:00
parent c71e7b399a
commit 8210619c7a
1 changed files with 20 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
doc/guide/admin/overlays.sdf
View File

@ -326,7 +326,7 @@ H3: Read-Back of Chained Modifications
Occasionally, applications want to read back the data that they just wrote. Occasionally, applications want to read back the data that they just wrote.
If a modification requested to a shadow server was silently chained to its If a modification requested to a shadow server was silently chained to its
producer, an immediate read could result in receiving data not yet sync'ed. producer, an immediate read could result in receiving data not yet synchronized.
In those cases, clients should use the {{B:dontusecopy}} control to ensure In those cases, clients should use the {{B:dontusecopy}} control to ensure
they are directed to the authoritative source for that piece of data. they are directed to the authoritative source for that piece of data.
@ -1099,16 +1099,31 @@ H2: Sync Provider
H3: Overview H3: Overview
This overlay implements the provider-side support for syncrepl This overlay implements the provider-side support for the LDAP Content Synchronization
replication, including persistent search functionality ({{REF:RFC4533}}) as well as syncrepl replication support, including persistent search functionality.
H3: Sync Provider Configuration H3: Sync Provider Configuration
There is very little configuration needed for this overlay, in fact for many situations merely loading
the overlay will suffice.
However, because the overlay creates a contextCSN attribute in the root entry of the database which is
updated for every write operation performed against the database and only updated in memory, it is
recommended to configure a checkpoint so that the contextCSN is written into the underlying database to
minimize recovery time after an unclean shutdown:
> overlay syncprov
> syncprov-checkpoint 100 10
For every 100 operations or 10 minutes, which ever is sooner, the contextCSN will be checkpointed.
The four configuration directives available are {{B:syncprov-checkpoint}}, {{B:syncprov-sessionlog}},
{{B:syncprov-nopresent}} and {{B:syncprov-reloadhint}} which are covered in the man page discussing
various other scenarios where this overlay can be used.
H3: Further Information H3: Further Information
{{:slapo-syncprov(5)}} The {{:slapo-syncprov(5)}} man page and the {{SECT:Configuring the different replication types}} section
H2: Translucent Proxy H2: Translucent Proxy