# MV\_AGGREGATED\_REPLICATION\_STATUS

This view provides the aggregated replication status of each database in the cluster.

Each row in this view corresponds to a specific type of replication (DR/non-DR) for each database in the cluster. This view can be accessed from any aggregator (`MA` or `CA`).

| Column name                   | Description                                                                                                      |
| ----------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| `is_dr`                       | Specifies if the row corresponds to a DR replication link.                                                       |
| `is_sync`                     | Specifies if the row corresponds to a synchronous replication link.                                              |
| `database_name`               | The name of the database in the current host.                                                                    |
| `primary_uri`                 | The URI of the primarycluster’s`MA`in the`host:port/source_db_name`format.                                       |
| `secondary_uri`               | The URI of the secondarycluster’s`MA`in the`host:port/source_db_name`format.                                     |
| `primary_state`               | The replication state of the primarycluster.                                                                     |
| `secondary_state`             | The replication state of the secondarycluster.                                                                   |
| `lsn_lag`                     | The total number of LSNs lagging to catch up with the primaryclusterfrom all nodes.                              |
| `volume_lag_mb`               | The total volume of lag, in megabytes (MB), from all nodes.                                                      |
| `replication_throughput_mbps` | The total throughput, in megabytes per second (MB/s), from all nodes.                                            |
| `estimated_catcup_time_s`     | The maximum time, in seconds, required by the secondaryclusterto catch up with the primaryclusterfrom all nodes. |

***

Modified at: April 1, 2025

Source: [/db/v9.1/reference/information-schema-reference/management/mv-aggregated-replication-status/](https://docs.singlestore.com/db/v9.1/reference/information-schema-reference/management/mv-aggregated-replication-status/)

(An index of the documentation is available at /llms.txt)