Replicator Server
The Replicator Server is a stand-alone process that sends changes prepared by the distribution threads to their respective targets. Once the transaction has been transmitted, the replications are secured on the target database and are removed from the distribution queue. The Replicator Server also detects and resolves collisions.
How the Replicator Server Process Works
After the distribution threads alert it, the Replicator Server completes the following tasks:
1. The Replicator Server reads the distribution queue.
2. The Replicator Server propagates each replicated row to the target database using direct SQL or database procedures over Ingres Net.
3. After propagating a set of rows in an original user transaction by CDDS, the server deletes the corresponding rows from the distribution queue.
4. The Replicator Server uses two-phase commit to update two databases. For more information, see How Two-phase Commit Works.
The Replicator Server also performs tasks such as checking the status of its Ingres Net connections. The following figure illustrates the tasks of the Replicator Server:
Last modified date: 08/14/2024