Content Server Manual / Version 2010
Table Of ContentsWhen a new content item is published on the Master Live Server, the replication process receives a change event and starts to read the content data from the Master Live Server. In rare cases, situations with potentially inconsistent data can arise:
In the time period between the change event and the content data transmission the relevant content items is destroyed.
To resolve this inconsistency the replication process waits until the destruction event for the corresponding content item has arrived.
The content item does exist but in the time period between the change event and the content data transmission the relevant version was destroyed.
Since there are only two content versions on a Live Server, this can only happen during a short period during publication or if a replicator which has not been running for a long period catches up. To fix this inconsistency, the replication process waits for the publication event of the new version and the deletion of the old version.
The replication process only resolves inconsistencies when the Replication Live Server is in "online" mode, since temporary inconsistencies must be avoided here.