All Products
Search
Document Center

ApsaraDB for MongoDB:Change the ConfigServer configuration

Last Updated:Aug 21, 2026

The ConfigServer component stores the metadata for a sharded environment, which includes cluster configuration information and the data distribution on each shard (which data resides on which Shard). When a ConfigServer cannot meet storage requirements or reaches a performance bottleneck, you can resolve the issue by scaling up its storage space or upgrading its specifications. ApsaraDB for MongoDB sharded cluster instances support configuration changes for ConfigServers.

Prerequisites

The instance uses ESSD.

Billing rules

For more information, see Configuration change fees.

Usage notes

  • The storage space that you select must be greater than or equal to the current storage space of the ConfigServer.

  • The configuration change may cause one or two transient disconnections, each lasting about 30 seconds. You can specify when the change takes effect to avoid business interruptions.

    Important

    When you change only the storage space, the system performs different operations depending on the available storage resources on the local host:

    • Sufficient: The system expands the storage on the local host, which does not require cross-host migration or a switchover. No transient disconnection occurs, and the change takes effect immediately without waiting for the maintenance window.

    • Insufficient: Cross-host migration and switchover are required. A transient disconnection occurs during the change, and the change takes effect at the switchover time that you specify.

  • The time required to complete the configuration change depends on multiple factors, such as network conditions, the task queue, and data volume. We recommend that you perform this operation during off-peak hours and ensure that your application has an automatic reconnection mechanism.

  • If your database's minor version is expired or no longer maintained, the system upgrades it to the latest minor version by default to ensure optimal performance and stability.

Procedure

  1. Go to the MongoDB sharded cluster instances page. Select a resource group and region at the top, and then click the ID of the target instance.

  2. On the Basic Information page, in the Configserver List section, perform the following operations:

    • Subscription instance: Click 三个点 in the row for the target ConfigServer and select Upgrade or Downgrade.

    • Pay-as-you-go instance: Click 三个点 in the row for the target ConfigServer and select Change configuration.

  3. Configure the following parameters.

    Parameter

    Description

    Category

    Select a new category for the ConfigServer.

    Note
    • Available only for cloud disk-based instances.

    • A category is unavailable if the current zone does not support it.

    • For information about the categories and specifications of sharded cluster instances, see Sharded cluster instance specifications.

    Change configuration

    Select new specifications and storage space for the ConfigServer.

    Note

    The selected storage space must be greater than or equal to the current storage space of the ConfigServer. To reduce storage space, create a new instance and migrate your data. For more information, see Other configuration change scenarios and methods.

    Switching Time

    Select when the change takes effect.

    • Switch Immediately After Task Completion: The system switches the instance as soon as the change is complete.

    • Switch Within Maintenance Window After Task Completion: The switchover takes effect within the maintenance window. You can use the current maintenance window or specify a new one based on your business requirements. For more information about maintenance windows, see Set a maintenance window.

  4. Complete the purchase based on your billing method.

    • For pay-as-you-go instances: Click Pay. The system automatically deducts the fee within the next hour.

    • For subscription instances: Click Pay, and then follow the instructions on the Pay page to complete the payment.

    During the configuration change, the instance status is In the process of matching. The change is complete when the instance status changes to Running.

Related APIs

API

Description

ModifyNodeSpec

Changes the configuration of a single Mongos, Shard, or ConfigServer node in an ApsaraDB for MongoDB sharded cluster instance.