ApsaraDB for MongoDB:Configure a primary/secondary switchover for a sharded cluster instance

Usage notes

• Primary/secondary switchover is supported only for ApsaraDB for MongoDB replica set and sharded cluster instances. This feature is not supported for standalone instances because of their architecture.

• The shard or ConfigServer component for which you want to trigger a primary/secondary switchover must be in the Running state.

• A primary/secondary switchover causes a transient connection error that lasts for up to 30 seconds. Perform this operation during off-peak hours and ensure that your application has a reconnection mechanism.

Procedure

1. Go to the MongoDB Sharded Cluster Instances page. In the top navigation bar, select a resource group and a region. Then, click the ID of the target instance.

2. In the navigation pane on the left, click Service Availability.

3. Click Switch Role to the right of the target shard or ConfigServer component.

4. In the Switch Role panel, select two roles and configure Effective At.

   • Effective Immediately: The system immediately performs primary/secondary switchover.

   • Effective Within Maintenance Window:The system performs primary/secondary switchover within the specified maintenance window. You can select the current maintenance window or specify a custom maintenance window in the Change Maintenance Window drop-down list.

5. Click OK.

   The instance status changes to Switching Role. When the status changes to Running, the switchover is successful.

   Note

   The switchover is complete in about one minute, and the instance status returns to Running.

6. Optional: To trigger a primary/secondary switchover for other shard or ConfigServer components in the ApsaraDB for MongoDB sharded cluster instance, repeat the preceding steps.

FAQ

Why does the high availability system of ApsaraDB for MongoDB trigger primary/standby switchover?

Related API operations