After you create a Global Active Database (GAD) instance group, open the instance group details page to check its status, topology, and member configurations.
Prerequisites
Before you begin, ensure that you have:
A GAD instance group already created
View instance group details
Go to the Global Active Instances page and click the ID of the instance group. The details page has three sections: Basic Information, Topology, and Configurations.
Basic information
The Basic Information section shows the following fields:
| Field | Description |
|---|---|
| Instance Group ID | Unique identifier for the instance group |
| Name | Display name of the instance group |
| Type | Type of the instance group |
| Database Type | Database engine used by the instance group |
| Created At | Date and time the instance group was created |
| State | Current operational state of the instance group |
| Region | Region where the instance group is deployed |
Topology
The topology view uses interrelated geometric objects to show the primary and secondary instances, the data synchronization tasks between them, and their current states.
From the topology view:
Click an instance ID to open the instance details page in the ApsaraDB RDS console.
Click a data synchronization task ID to open the task details page in the Data Transmission Service (DTS) console.
Configurations
The Configurations section lists all RDS instances and DTS instances in the group.
ApsaraDB RDS instances
The ApsaraDB RDS Instances tab shows each instance's State, Region/Zone, Role, and Created At.
Click an instance ID to view its details.
Click Add Secondary Instance in the upper-right corner to add an RDS instance as a secondary instance to the group.
Click Remove in the Actions column to remove a secondary instance from the group.
DTS instances
The DTS Instances tab shows each DTS instance's synchronization direction, Region, State, Synchronization Latency, and Created At.
Click the DTS Instance ID or Details to view the data synchronization task details.
When you remove a secondary instance from the group, the associated DTS synchronization task is automatically released. No manual action is required.