Inconsistent data when transaction updates are replicated

There is a possibility of inconsistent data on a directory server when transaction updates are replicated in an environment with failover setup.

When transactional updates are replicated by a supplier, the updates are not replicated in a transactional manner by the supplier to its consumers. In a replicated environment, the supplier replicates the transactional updates to its consumers only when the transaction is complete (committed or rolled back state). If a supplier goes offline during replication of the transactional updates, it is possible that only a part of the update is replicated to its consumers. In this case, when the supplier is brought online the remaining updates that are in its replication queue is replicated automatically.

However, in a replication environment with failover, if the primary master fails during replication of updates, the proxy server fails over to the peer server. The data might not be entirely consistent because it is possible for the peer server to not get all the updates made to master.