DocsICP FilingConsole
官方文档
首页

Limitations

更新时间：
复制 MD 格式
产品详情
我的收藏

Before you use ApsaraDB for MongoDB, you must understand the constraints of different instance types. This topic describes these limitations to help you select the right instance for your business.

Standalone instance

Feature

Constraint

Instance deployment

Standalone instances are not supported in all regions and zones. For details, see Supported regions and zones.

Database version

Only ApsaraDB for MongoDB 3.4 and 4.0 support standalone instances.

Important

ApsaraDB for MongoDB 3.4 has been unavailable for purchase since January 1, 2023. For more information, see [Notice] End of sale for MongoDB 3.4 instances as of January 1, 2023.

Database connection

You cannot enable or disable encryption for private connections.

Data backup

Only Snapshot Backup is supported.

Note

A snapshot backup preserves the disk data state at a specific point in time.

Data restoration

Service availability

High availability features such as primary/secondary switchover, role switchover, and cross-zone migration are not supported.

Data security

Log management

Log management is not supported, including Slow Query Logs, Error Logs, and Running Logs.

CloudDBA

  • Only Performance is supported.

  • Real-time Performance, Sessions, Storage Analysis, and Slow Query Logs are not supported.

Data migration and synchronization

Replica set instance

Feature

Constraint

Instance deployment

Replica set instances are not supported in all regions and zones. For details, see Supported regions and zones.

Minor version

To ensure optimal performance and stability, the system automatically upgrades an expired or unmaintained minor version to the latest version during operations such as major version upgrades, data migration, configuration changes, or data restoration.

Database connection

For replica set instances that run MongoDB 4.4 or later, you cannot switch the network type from classic network to VPC.

Data backup

  • Replica set instances that run MongoDB 3.4, 4.0, and 4.2 support Physical Backup and Logical Backup.

    Note

    For an instance running MongoDB 3.4, the total number of collections and indexes must be less than 10,000. Otherwise, physical backups may fail. If you expect to exceed this limit, we recommend that you create an instance that runs MongoDB 4.0 or 4.2, or upgrade the database version to 4.0 or 4.2. For more information, see Upgrade the major version of an instance.

  • Replica set instances that run MongoDB 4.4 or later support Snapshot Backup.

    Note

    A snapshot backup preserves the disk data state at a specific point in time.

Data security

Log management

No limitations.

CloudDBA

No limitations.

Data migration and synchronization

Sharded cluster instance

Feature

Constraint

Instance deployment

Sharded cluster instances are not supported in all regions and zones. For details, see Supported regions and zones.

Minor version

To ensure optimal performance and stability, the system automatically upgrades an expired or unmaintained minor version to the latest version during operations such as major version upgrades, data migration, configuration changes, or data restoration.

Data reads and writes

The admin database in a sharded cluster instance is read-only.

Data backup

Sharded cluster instances support Physical Backup and Logical Backup.

Data restoration

Only point-in-time restoration to a new instance is supported. For more information, see Restore data to a new instance by point in time.

Data security
Note

DynamoDB-compatible sharded cluster instances support only VPC. To create a VPC, see Create and manage a VPC.

CloudDBA

DynamoDB-compatible sharded cluster instances do not support CloudDBA, including Performance, Real-time Performance, Sessions, Storage Analysis, and Slow Query Logs.

Data migration and synchronization

Recycle bin

The recycle bin feature is not supported.

Serverless instance

Feature

Constraint

Modify instance parameters

You cannot modify the parameters of a serverless instance.

Data reads and writes

  • The number of databases is limited to 20, and the number of collections is limited to 500.

  • The admin database in a serverless instance is read-only.

Database connection

  • You cannot enable or disable password-free access over a private network.

  • You cannot switch the network type from classic network to VPC.

Data backup and restoration

You can only use MongoDB tools (mongodump and mongorestore) for data backup and restoration. For more information, see Use MongoDB tools to back up and restore an ApsaraDB for MongoDB serverless instance.

Data security

  • Only whitelists are supported. For configuration instructions, see Configure a whitelist for an instance.

  • SSL encryption and TDE are not supported.

  • The audit log feature is not supported.

Log management

Serverless instances do not support log management, including Slow Query Logs, Error Logs, and Running Logs.

CloudDBA

Serverless instances do not support CloudDBA, including Performance, Real-time Performance, Sessions, Storage Analysis, and Slow Query Logs.

Data migration and synchronization

You can migrate data from a serverless instance by using the following methods:

Recycle bin

The recycle bin feature is not supported.

Restart instance

You cannot restart a serverless instance.
Previous：TermsNext：Billing