From 8e906885ab9d0a98799e6b595c4104109dafbbee Mon Sep 17 00:00:00 2001
From: Mark Craig <mark.craig@forgerock.com>
Date: Tue, 12 May 2015 16:19:13 +0000
Subject: [PATCH] Clarify limits of replication topologies
---
opendj-server-legacy/src/main/docbkx/admin-guide/chap-replication.xml | 13 ++++++++-----
1 files changed, 8 insertions(+), 5 deletions(-)
diff --git a/opendj-server-legacy/src/main/docbkx/admin-guide/chap-replication.xml b/opendj-server-legacy/src/main/docbkx/admin-guide/chap-replication.xml
index acaf196..cea07d6 100644
--- a/opendj-server-legacy/src/main/docbkx/admin-guide/chap-replication.xml
+++ b/opendj-server-legacy/src/main/docbkx/admin-guide/chap-replication.xml
@@ -199,11 +199,14 @@
</textobject>
</mediaobject>
- <para>Within a replication topology, the suffixes being replicated are
- identified to the replication servers by their DN. As all the replication
- servers are fully connected in a topology, a consequence is that it is
- impossible to have multiple "sub-topologies" within the overall set of
- servers as illustrated in the following diagram.</para>
+ <para>
+ Within a replication topology,
+ the suffixes being replicated are identified to the replication servers by their DNs.
+ All the replication servers are fully connected in a topology.
+ Consequently it is impossible to have multiple separate, independent topologies
+ for data under the same DN within the overall set of servers.
+ This is illustrated in the following diagram.
+ </para>
<mediaobject xml:id="figure-replication-topologies-wrong">
<alt>Two replication topologies, one of which does not work</alt>
--
Gitblit v1.10.0