View how the nodes of a replica set or sharded cluster instance are distributed across zones. Use this information to confirm your high availability (HA) topology and plan zone migration or node role changes.
Prerequisites
Before you begin, ensure that:
The instance is a replica set instance or sharded cluster instance
How it works
ApsaraDB for MongoDB deploys the nodes of a replica set or sharded cluster instance across three zones in the same region. This zone-disaster recovery deployment keeps your data available if one zone becomes unavailable due to force majeure factors such as a power or network failure — the HA system automatically fails over to another zone.
For more information about how to create a multi-zone instance, see Create a multi-zone replica set instance and Create a multi-zone sharded cluster instance.
For details on multi-zone versus single-zone deployment, see the "Node deployment policies" section of Create a multi-zone replica set instance and Create a multi-zone sharded cluster instance.
View zone distribution
Log on to the ApsaraDB for MongoDB console.
In the left-side navigation pane, click Replica Set Instances or Sharded Cluster Instances.
In the upper-left corner of the page, select the resource group and region where the instance is located.
Click the ID of the instance, or click Manage in the Actions column.
In the left-side navigation pane, click Service Availability. In the Zone Distribution section, view the zone assigned to each node.
What's next
Migrate an ApsaraDB for MongoDB instance to different zones in the same region
Move an instance from a single zone to multiple zones, or between zones in the same region. The instance attributes, specifications, and endpoint remain unchanged after migration.
Reassign node roles so your applications connect to the nearest nodes based on your deployment topology.