Why is priority synchronization sending critical and non-critical
data to other servers?
What is the object transaction model?
This is normal, expected behavior. All versions of eDirectory
implement the object transaction model. Simply put, this model
specifies that changes are applied in the same order that they come
into eDirectory. If title is changed then last name is updated,
every server will get the updates in that order. The last name
update will not come before the title change.
In order for priority synchronization to maintain the
object transaction model, it has to ensure that any pending changes
to non-critical data are also sent with changes to critical data.
Using the above example, an administrator could setup a priority
synchronization policy for the last name attribute. If a user's
title is changed, that modification is not immediately sent out.
When the user's last name is updated, priority synchronization will
immediately send out the title change and last name update to every
other server holding a copy of the partition.
For more details on priority synchronization and the object
transaction model, see the relevant section in the Novell 8.8 eDirectory