Skip to content
Snippets Groups Projects
Commit 2147b25b authored by Quanah Gibson-Mount's avatar Quanah Gibson-Mount
Browse files

delta-syncrepl png and svg files.

n-way-multimaster png and svg files.
First attempt to visualise refreshOnly and refreshAndPersist modes of LDAP Sync Protocol.
parent 1dd4c105
No related branches found
No related tags found
No related merge requests found
doc/guide/admin/delta-syncrepl.png

55.2 KiB

doc/guide/admin/ldap-sync-refreshandpersist.png

69.9 KiB

doc/guide/admin/ldap-sync-refreshonly.png

66.4 KiB

doc/guide/admin/n-way-multi-master.png

45.5 KiB

...@@ -245,7 +245,7 @@ time the provider reads the last saved {{EX:contextCSN}} into memory ...@@ -245,7 +245,7 @@ time the provider reads the last saved {{EX:contextCSN}} into memory
and uses the in-memory copy exclusively thereafter. By default, and uses the in-memory copy exclusively thereafter. By default,
changes to the {{EX:contextCSN}} as a result of database updates changes to the {{EX:contextCSN}} as a result of database updates
will not be written to the database until the server is cleanly will not be written to the database until the server is cleanly
shut down. A checkpoint facility exists to cause the contextCSN to shut down. A checkpoint facility exists to cause the {{EX:contextCSN}} to
be written out more frequently if desired. be written out more frequently if desired.
Note that at startup time, if the provider is unable to read a Note that at startup time, if the provider is unable to read a
...@@ -291,7 +291,7 @@ specification, it is possible for a modification to remove an entry ...@@ -291,7 +291,7 @@ specification, it is possible for a modification to remove an entry
from the replication scope even though the entry has not been deleted from the replication scope even though the entry has not been deleted
on the provider. Logically the entry must be deleted on the consumer on the provider. Logically the entry must be deleted on the consumer
but in {{refreshOnly}} mode the provider cannot detect and propagate but in {{refreshOnly}} mode the provider cannot detect and propagate
this change without the use of the session log. this change without the use of the session log on the provider.
For configuration, please see the {{SECT:Syncrepl}} section. For configuration, please see the {{SECT:Syncrepl}} section.
......
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment