Red Hat Directory Server 8.0 Administrator's Guide

Enabling the Attribute Uniqueness Plug-in on the consumer does not prevent Directory Server
from operating correctly but is likely to cause a performance degradation.
6.2. Multi-Master Replication Scenario
In a multi-master replication scenario, the masters act both as suppliers and consumers of the
same replica. Because multi-master replication uses a loosely consistent replication model,
enabling an Attribute Uniqueness Plug-in on one of the servers is not sufficient to ensure that
attribute values will be unique across both supplier servers at any given time. Therefore,
enabling an Attribute Uniqueness Plug-in on one server can cause inconsistencies in the data
held on each replica.
However, it is possible to use an Attribute Uniqueness Plug-in, providing both of the following
conditions are met:
• The attribute on which the uniqueness check is performed is a naming attribute.
• The Attribute Uniqueness Plug-in is enabled on both supplier servers.
When these conditions are met, attribute uniqueness conflicts are reported as naming conflicts
at replication time. Naming conflicts require manual resolution. For information on how to
resolve replication conflicts, see Section 18, “Solving Common Replication Conflicts”.
Multi-Master Replication Scenario
513