|
|
|
When DISP resynchronization starts, it propagates all the changes to the DSA since the last successful multiwrite update.
In a multimaster system, it is possible for some changes to clash. In practice this is exceedingly rare. The window for discrepancy is small and all running master DSAs keep themselves synchronized using multiwrite. However, CA Directory resolves such conflicts automatically, using a last-write-wins rule. The granularity of reconciliation is an X.500 object.
Example: Conflict Resolution
If DSA 1 updates an object's surname attribute at time T, and DSA 2 updates an object's phoneNumber attribute at time T+1, then the final object after resynchronization is the object contained in DSA 2. This does not have the changes to the surname.
| Copyright © 2009 CA. All rights reserved. | Email CA about this topic |