To improve user experience, ApsaraDB for MongoDB adjusted the maximum number of connections to ApsaraDB for MongoDB instances of specific specifications on May 14, 2024. By default, the new maximum number of connections applies to ApsaraDB for MongoDB instances that are purchased after the adjustment. For existing ApsaraDB for MongoDB instances, the new maximum number of connections takes effect after the instances are restarted. The adjustment does not affect other services of ApsaraDB for MongoDB.
Effective time
May 14, 2024
Scope
ApsaraDB for MongoDB instances of specific specifications
Content
The maximum number of connections to ApsaraDB for MongoDB instances of specific specifications is increased. The following tables describe the original and new maximum numbers of connections to ApsaraDB for MongoDB instances of different categories.
Dedicated instances that use cloud disks
Instance architecture | Specifications | Instance type | Original maximum number of connections | New maximum number of connections |
| 2 cores, 8 GB memory | mdb.shard.4x.large.d | 3000 | 5000 |
2 cores, 16 GB memory | mdb.shard.8x.large.d | 5000 | 8000 | |
4 cores, 8 GB memory | mdb.shard.2x.xlarge.d | 3000 | 8000 | |
4 cores, 16 GB memory | mdb.shard.4x.xlarge.d | 5000 | 8000 | |
4 cores, 32 GB memory | mdb.shard.8x.xlarge.d | 8000 | 12000 | |
8 cores, 16 GB memory | mdb.shard.2x.2xlarge.d | 5000 | 12000 | |
8 cores, 32 GB memory | mdb.shard.4x.2xlarge.d | 8000 | 16000 | |
16 cores, 32 GB memory | mdb.shard.2x.4xlarge.d | 8000 | 16000 | |
16 cores, 64 GB memory | mdb.shard.4x.4xlarge.d | 16000 | 32000 | |
16 cores, 128 GB memory | mdb.shard.8x.4xlarge.d | 16000 | 32000 | |
32 cores, 64 GB memory | mdb.shard.2x.8xlarge.d | 16000 | 32000 | |
32 cores, 128 GB memory | mdb.shard.4x.8xlarge.d | 16000 | 96000 | |
32 cores, 256 GB memory | mdb.shard.8x.8xlarge.d | 16000 | 96000 | |
64 cores, 128 GB memory | mdb.shard.2x.16xlarge.d | 64000 | 96000 | |
64 cores, 256 GB memory | mdb.shard.4x.16xlarge.d | 64000 | 128000 | |
64 cores, 512 GB memory | mdb.shard.8x.16xlarge.d | 64000 | 128000 |
General-purpose instances that use cloud disks
Instance architecture | Specifications | Instance type | Original maximum number of connections | New maximum number of connections |
| 2 cores, 4 GB memory | mdb.shard.2x.large.c | 1000 | 3000 |
4 cores, 8 GB memory | mdb.shard.2x.xlarge.c | 3000 | 6000 | |
4 cores, 16 GB memory | mdb.shard.4x.xlarge.c | 5000 | 6000 | |
8 cores, 16 GB memory | mdb.shard.2x.2xlarge.c | 5000 | 12000 | |
8 cores, 32 GB memory | mdb.shard.4x.2xlarge.c | 8000 | 16000 | |
16 cores, 32 GB memory | mdb.shard.2x.4xlarge.c | 8000 | 16000 | |
16 cores, 64 GB memory | mdb.shard.4x.4xlarge.c | 16000 | 32000 | |
32 cores, 64 GB memory | mdb.shard.2x.8xlarge.c | 16000 | 32000 |
Dedicated instances that use local disks
Instance architecture | Specifications | Instance type | Original maximum number of connections | New maximum number of connections |
Replica set instance | 2 cores, 16 GB memory | mongo.x8.medium | 2500 | 8000 |
4 cores, 32 GB memory | mongo.x8.large | 5000 | 8000 | |
8 cores, 64 GB memory | mongo.x8.xlarge | 10000 | 16000 | |
16 cores, 128 GB memory | mongo.x8.2xlarge | 20000 | 32000 | |
32 cores, 256 GB memory | mongo.x8.4xlarge | 40000 | 64000 | |
Sharded cluster instance | 8 cores, 64 GB memory | dds.shard.sn8.4xlarge.3 | 8000 | 16000 |
16 cores, 128 GB memory | dds.shard.sn8.8xlarge.3 | 16000 | 32000 | |
32 cores, 256 GB memory | dds.shard.sn8.16xlarge.3 | 32000 | 64000 |
General-purpose instances that use local disks
Instance architecture | Specifications | Instance type | Original maximum number of connections | New maximum number of connections |
Replica set instance | 1 core, 2 GB memory | dds.mongo.mid | 500 | 1000 |
2 cores, 4 GB memory | dds.mongo.standard | 1000 | 3000 | |
4 cores, 8 GB memory | dds.mongo.large | 3000 | 6000 | |
8 cores, 16 GB memory | dds.mongo.xlarge | 5000 | 9000 | |
8 cores, 32 GB memory | dds.mongo.2xlarge | 8000 | 16000 | |
16 cores, 64 GB memory | dds.mongo.4xlarge | 16000 | 32000 | |
Sharded cluster instance | 2 cores, 4 GB memory | dds.mongos.standard | 2000 | 3000 |
4 cores, 8 GB memory | dds.mongos.large | 4000 | 6000 | |
8 cores, 16 GB memory | dds.mongos.xlarge | 8000 | 9000 | |
16 cores, 64 GB memory | dds.mongos.4xlarge | 16000 | 32000 |
The preceding tables show the original and new maximum numbers of connections to instances of specifications only involved in this adjustment. For more information about the maximum number of connections to instances of other specifications, see Instance types.
Take note of the following items:
For ApsaraDB for MongoDB instances that are purchased after the adjustment, the new maximum number of connections immediately takes effect after the instances are purchased.
For existing ApsaraDB for MongoDB instances, the new maximum number of connections takes effect after the instances are restarted.
Impacts
The new maximum number of connections does not take effect on existing ApsaraDB for MongoDB instances until the instances are restarted. Before the instances are restarted, the maximum number of connections to the instances remains unchanged. For more information about how to restart an instance, see Restart an ApsaraDB for MongoDB instance or a node.
The adjustment does not affect other services of ApsaraDB for MongoDB.
A larger number of concurrent connections consume more resources such as CPU and memory. We recommend that you adjust the number of connections to your instance based on your business requirements.
If you have any questions, submit a ticket.