mirror of https://github.com/OpenIdentityPlatform/OpenDJ.git

Mark Craig
12.19.2015 8e906885ab9d0a98799e6b595c4104109dafbbee
Clarify limits of replication topologies

The Admin Guide section describing replication topologies
introduces the idea of “sub-topologies” without explaining it.
This patch clarifies what is meant,
and breaks up a long sentence to make the text easier to digest.

Thanks to Fabio for pointing out the problem and reviewing over IM.
1 files modified
13 ■■■■■ changed files
opendj-server-legacy/src/main/docbkx/admin-guide/chap-replication.xml 13 ●●●●● patch | view | raw | blame | history
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>