Modification conflict scenarios
Modification conflicts resolve automatically and no manual action is required. The LDAPModify operation allows the following modification types:
-
Add of one or more values
-
Delete of one or more values or the entire attribute
-
Replacement of all values
|
Replication does not currently support the increment LDAP modification type. |
The following illustration presents a modification conflict scenario.
- Processing steps
-
-
LDAP client A sends a
modifyrequest to directory server A. -
LDAP client B sends a conflicting
modifyrequest to directory server B. -
Directory server A applies the modification.
-
Directory server B applies the modification.
-
The LDAP clients receive successful responses.
-
Replication propagates the updates.
-
Conflict resolution on directory server A updates the entry to reflect the value on directory server B.
Conflict resolution on directory server B ignores the update received from directory server A.
-
The following table shows the result of a modification conflict depending on the type of updates that occur. For all of the operations in the table, assume the following:
-
LDAP Modify 1 was applied at PingDirectory server 1.
-
LDAP Modify 2 was applied at PingDirectory server 2.
-
LDAP Modify 1 occurred shortly before LDAP Modify 2, so that PingDirectory server 2 received LDAP Modify 1 after LDAP Modify 2 was applied.
| Modify 1 | Modify 2 | Result of Conflict Resolution at PingDirectory server 2 When Modify 1 is received |
|---|---|---|
|
|
Incoming |
|
Replacement of the value of the same attribute |
Incoming |
Replacement of a single-valued attribute |
|
Incoming Replacement is ignored. |
|
|
Incoming |
|
|
Incoming |
|
|
Incoming |
|
|
Incoming |
|
|
|
|
|
|
|
Replace all values of the same multi-valued attribute |
Incoming |
|
|
Only value Y is added. |
|
|
Incoming |