The problem is mostly caused by the evaluation of timestamps, when processing changes.

In scenarios where changes can come from several replicas and you don’t control the order at which replication will change, this is problematic. In certain circumstances you would need a way to force sync to sync changes in the order they are made.

Workarounds like stripping timestamps or moving related drivers to one server only are not always feasable (RRSD has to run on UA server always for instance).

One forum thread where Father Ramon commented on this:
https://groups.google.com/forum/#!topic/novell.support.nsure-identity-manager/yh1muJ6kGnc
"...the problem you are having is because you have multiple replicas
of the partition you are synchronizing and time on one of the other
replica servers is ahead of the time on the DirXML server. ..."

From our point of view, an ECV (Engine Control Value) would be a good solution. This ECV should be able to steer the engine optimisations for the "Synthetic Add". That would be easier to handle for customers and would promote this problem at multiserver environments into the focus. We think for most customers, it is not obvious that this effect can occur.

by: Karl P. | over a year ago | Other