Effective May 14, 2024, ApsaraDB for MongoDB increased the maximum connection limits for 42 instance specifications across four categories, with increases of up to 6x for select instance types.
| Detail | Description |
|---|---|
| Effective date | May 14, 2024 |
| Scope | Specific instance types across replica set and sharded cluster instances |
| New instances | New limits apply automatically |
| Existing instances | New limits take effect after a restart |
Updated connection limits
The following tables list the previous and updated maximum connection limits for each affected instance type. For connection limits of unaffected instance types, see Instance types.
Dedicated instances (cloud disks)
Applies to both replica set instances and sharded cluster instances.
| Specifications | Instance type | Previous limit | New limit |
|---|---|---|---|
| 2 cores, 8 GB memory | mdb.shard.4x.large.d | 3,000 | 5,000 |
| 2 cores, 16 GB memory | mdb.shard.8x.large.d | 5,000 | 8,000 |
| 4 cores, 8 GB memory | mdb.shard.2x.xlarge.d | 3,000 | 8,000 |
| 4 cores, 16 GB memory | mdb.shard.4x.xlarge.d | 5,000 | 8,000 |
| 4 cores, 32 GB memory | mdb.shard.8x.xlarge.d | 8,000 | 12,000 |
| 8 cores, 16 GB memory | mdb.shard.2x.2xlarge.d | 5,000 | 12,000 |
| 8 cores, 32 GB memory | mdb.shard.4x.2xlarge.d | 8,000 | 16,000 |
| 16 cores, 32 GB memory | mdb.shard.2x.4xlarge.d | 8,000 | 16,000 |
| 16 cores, 64 GB memory | mdb.shard.4x.4xlarge.d | 16,000 | 32,000 |
| 16 cores, 128 GB memory | mdb.shard.8x.4xlarge.d | 16,000 | 32,000 |
| 32 cores, 64 GB memory | mdb.shard.2x.8xlarge.d | 16,000 | 32,000 |
| 32 cores, 128 GB memory | mdb.shard.4x.8xlarge.d | 16,000 | 96,000 |
| 32 cores, 256 GB memory | mdb.shard.8x.8xlarge.d | 16,000 | 96,000 |
| 64 cores, 128 GB memory | mdb.shard.2x.16xlarge.d | 64,000 | 96,000 |
| 64 cores, 256 GB memory | mdb.shard.4x.16xlarge.d | 64,000 | 128,000 |
| 64 cores, 512 GB memory | mdb.shard.8x.16xlarge.d | 64,000 | 128,000 |
General-purpose instances (cloud disks)
Applies to both replica set instances and sharded cluster instances.
| Specifications | Instance type | Previous limit | New limit |
|---|---|---|---|
| 2 cores, 4 GB memory | mdb.shard.2x.large.c | 1,000 | 3,000 |
| 4 cores, 8 GB memory | mdb.shard.2x.xlarge.c | 3,000 | 6,000 |
| 4 cores, 16 GB memory | mdb.shard.4x.xlarge.c | 5,000 | 6,000 |
| 8 cores, 16 GB memory | mdb.shard.2x.2xlarge.c | 5,000 | 12,000 |
| 8 cores, 32 GB memory | mdb.shard.4x.2xlarge.c | 8,000 | 16,000 |
| 16 cores, 32 GB memory | mdb.shard.2x.4xlarge.c | 8,000 | 16,000 |
| 16 cores, 64 GB memory | mdb.shard.4x.4xlarge.c | 16,000 | 32,000 |
| 32 cores, 64 GB memory | mdb.shard.2x.8xlarge.c | 16,000 | 32,000 |
Dedicated instances (local disks)
| Architecture | Specifications | Instance type | Previous limit | New limit |
|---|---|---|---|---|
| Replica set instance | 2 cores, 16 GB memory | mongo.x8.medium | 2,500 | 8,000 |
| Replica set instance | 4 cores, 32 GB memory | mongo.x8.large | 5,000 | 8,000 |
| Replica set instance | 8 cores, 64 GB memory | mongo.x8.xlarge | 10,000 | 16,000 |
| Replica set instance | 16 cores, 128 GB memory | mongo.x8.2xlarge | 20,000 | 32,000 |
| Replica set instance | 32 cores, 256 GB memory | mongo.x8.4xlarge | 40,000 | 64,000 |
| Sharded cluster instance | 8 cores, 64 GB memory | dds.shard.sn8.4xlarge.3 | 8,000 | 16,000 |
| Sharded cluster instance | 16 cores, 128 GB memory | dds.shard.sn8.8xlarge.3 | 16,000 | 32,000 |
| Sharded cluster instance | 32 cores, 256 GB memory | dds.shard.sn8.16xlarge.3 | 32,000 | 64,000 |
General-purpose instances (local disks)
| Architecture | Specifications | Instance type | Previous limit | New limit |
|---|---|---|---|---|
| Replica set instance | 1 core, 2 GB memory | dds.mongo.mid | 500 | 1,000 |
| Replica set instance | 2 cores, 4 GB memory | dds.mongo.standard | 1,000 | 3,000 |
| Replica set instance | 4 cores, 8 GB memory | dds.mongo.large | 3,000 | 6,000 |
| Replica set instance | 8 cores, 16 GB memory | dds.mongo.xlarge | 5,000 | 9,000 |
| Replica set instance | 8 cores, 32 GB memory | dds.mongo.2xlarge | 8,000 | 16,000 |
| Replica set instance | 16 cores, 64 GB memory | dds.mongo.4xlarge | 16,000 | 32,000 |
| Sharded cluster instance | 2 cores, 4 GB memory | dds.mongos.standard | 2,000 | 3,000 |
| Sharded cluster instance | 4 cores, 8 GB memory | dds.mongos.large | 4,000 | 6,000 |
| Sharded cluster instance | 8 cores, 16 GB memory | dds.mongos.xlarge | 8,000 | 9,000 |
| Sharded cluster instance | 16 cores, 64 GB memory | dds.mongos.4xlarge | 16,000 | 32,000 |
Impact on existing instances
The new connection limits do not take effect on existing instances until a restart. Before the restart, the previous limits remain in effect. For restart instructions, see Restart an ApsaraDB for MongoDB instance or a node.
Instances purchased after May 14, 2024 use the new limits automatically. No other ApsaraDB for MongoDB services are affected.
Usage notes
Higher concurrent connections consume more CPU and memory. Adjust connection limits based on actual workload requirements and monitor resource usage to avoid performance degradation.
If you have questions about this change, submit a ticket.