All Products
Search
Document Center

ApsaraDB for MongoDB:Change Mongos configurations

Last Updated:Mar 28, 2026

A Mongos routes client requests to the correct shard. When client traffic or request volume exceeds your Mongos nodes' capacity, change their specifications. ApsaraDB for MongoDB sharded cluster instances support changing the specifications of one or more Mongos nodes at a time.

Billing

Configuration changes may incur additional charges. For pricing details, see Configuration change fees.

Before you begin

Review the following considerations before starting the change.

Service interruptions

The change may cause 1–2 brief disconnections, each lasting about 30 seconds. Make sure your application has an automatic reconnection mechanism. To minimize business impact, schedule the change during off-peak hours.

Completion time

The time to complete the change depends on network conditions, the task queue, and the amount of data.

Automatic minor version upgrade

If your database's minor version has expired or is not on the maintenance list, the system automatically upgrades it to the latest minor version during the change to improve performance and stability.

Prerequisites

Before you begin, ensure that you have:

  • An ApsaraDB for MongoDB sharded cluster instance

  • Identified whether to change a single Mongos node or multiple nodes

  • Determined the target specifications (see Sharded cluster instance specifications)

Note

The available specifications depend on your current zone. If a specification category is not selectable, the current zone does not support it.

Change Mongos node specifications

  1. Go to the ApsaraDB for MongoDB sharded cluster instances page. At the top of the page, select a resource group and a region, then click the ID of the target instance.

  2. In the Mongos List section, start the configuration change:

    • Single node: Find the target Mongos node. In the Actions column, click the 三个点 icon, then select the appropriate option:

      • Pay-as-you-go: Change Configurations

      • Subscription: Upgrade Configuration or Downgrade Configuration

    • Multiple nodes:

      1. In the Mongos List, select the target Mongos nodes.

      2. In the upper-left corner of the Mongos List, select the appropriate option:

        • Pay-as-you-go: Batch Change

        • Subscription: Batch Upgrade or Batch Downgrade

  3. Set the parameters.

    ParameterDescription
    Specification categoryThe specification category for the Mongos nodes. Required only for instances that use cloud disks. If a category is unavailable, the current zone does not support it. For details, see Sharded cluster instance specifications.
    Instance SpecificationsThe specifications for the Mongos nodes.
    Switchover TimeWhen the configuration change takes effect. See the options below.

    Switchover time options

    OptionBehavior

    Switch Immediately after Migration

    Applies the change as soon as the migration task completes.

    Switch within Maintenance Window

    Applies the change during the scheduled maintenance window. To adjust the window, click Edit next to Switch within Maintenance Window, or click Edit next to Maintenance window in the Specification information section. For instructions, see Set a maintenance window.
    Note

    If you are unsure which option to choose, select Switch within maintenance window to reduce the risk of unexpected interruptions to production traffic.

  4. Complete the purchase.

    • Pay-as-you-go: Click Pay Now. The fee is deducted automatically within the next hour.

    • Subscription: Click Pay Now and complete payment on the Payment page.

While the change is in progress, the instance status is Changing Configuration. When the status changes to Running, the change is complete.

API reference

APIDescription
ModifyNodeSpecChanges the configuration of a single Mongos or shard node.
ModifyNodeSpecBatchChanges the configurations of multiple Mongos or shard nodes.