For all of the naming conflict scenarios in the table below, assume the folloing:
  • Update 1 was applied at Directory Server 1
  • Update 2 was applied at Directory Server 2
  • Update 1 occurred shortly before Update 2, so that Directory Server 2 received Update 1 after Update 2 was applied

The naming conflict scenario is illustrated in the following figure:

Replication Naming Conflicts
The following table shows the result of a modification conflict depending on the type of updates that occurs. The code does not compare change sequence numbers (CSNs) but applies operations in the order they were received. This may lead to inconsistent replays.
Update 1 Update 2 Automatic Resolution? Result of Conflict Resolution at Directory Server 2 When Update 1 is received
Modify Delete Yes Modify is discarded.
Modify Modify DN Yes New entry is located based on the entryUUID and Modify is applied to the renamed entry.
Delete Delete Yes Delete operation is ignored.
Delete Modify DN Yes

Delete operation is applied to the renamed entry.
Delete of A Add of B under A Yes

Entry B is renamed and Entry A is deleted.
Modify DN Delete of the same entry targeted by the Modify DN Yes

Modify DN operation is ignored.
Modify DN with a new parent Delete of parent No The entry targeted in the Modify DN operation is marked as a conflict entry.
Modify DN with a new parent Modify DN of the parent Yes

The entry will be moved under the new DN of the parent.
Modify DN of A with new DN B Modify DN of C with new DN B No A and B will be conflict entries.
Add A Modify DN of the parent of A Yes The entry is added under the new DN of the parent.
Add A Delete of the parent of A No The added entry is marked as a conflict entry.
Add A Add A with same set of attributes Yes The entryUUID of the incoming Add operation applied to the existing entry.
Add A Add A with different set of attributes (or values) No The existing entry is marked as a conflicting entry and the incoming Add is executed.