You can check the replication status using one of the following methods:
- On "Site B", run the following command:
ansible-playbook -i <inventoryFile-SiteB> tools/htap-multi-dc-manager.yml -u remote_user -bkKSelect 4 when prompted.
OR
- You can identify the lag in the replication process by checking the replication
status of each database (including partitions) and the replication links between the
primary and the secondary clusters. A value "zero" in either LSN_LAG or ESTIMATED_CATCHUP_TIME_S columns indicate that the replication is complete on the secondary cluster.
information_schema.MV_AGGREGATED_REPLICATION_STATUS
The features of the MV_AGGREGATED_REPLICATION_STATUS view are:
- It can be accessed from any aggregator
- It provides the aggregated replication status for each database in the cluster
- It has partitions of a database aggregated into a single row
- It provides a specific type of replication (DR/non-DR) in each row.
