The architecture of ApsaraDB for MongoDB standalone instances needs to be optimized. To meet the requirements for the optimization, Alibaba Cloud rolls out a new instance type that provides 8 cores and 32 GB of memory. Alibaba Cloud also temporarily deprecates the instance type that provides 1 core and 2 GB of memory, the instance that provides 2 cores and 4 GB of memory, and the instance type that provides 2 cores and 8 GB of memory.
Time
April 21, 2021
Specification changes
The following table describes the instance type that is rolled out and the instance types that are deprecated for ApsaraDB for MongoDB standalone instances.
| Adjustment type | Instance family | Specification | Instance type | Maximum connections | Maximum IOPS | Storage capacity |
|---|---|---|---|---|---|---|
| Rolled out | General mode | 8 cores, 32 GB of memory | dds.sn4.2xlarge.1 | 10000 | min {30 × Storage capacity, 20,000} | 20~2000 GB |
| Removed feature | 1 core and 2 GB of memory | dds.n2.small.1 | 2000 | |||
| 2 cores and 4 GB of memory | dds.sn2.medium.1 | 4000 | ||||
| 2 cores and 8 GB of memory | dds.sn4.large.1 | 6000 |
Impacts
If your standalone instance uses one of the deprecated instance types, the instance is subject to specific limits when you perform the following operations:
- Expand the storage capacity of the instance.
- Instance type
Solution
If your standalone instance uses one of the deprecated instance types, you can use one of the following solutions to mitigate the impacts of the adjustments:
- Upgrade the instance type of your standalone instance to an instance type that provides four or more cores. For more information, see Change the configurations of a standalone instance.
- Switch the workloads in your standalone instance over to a new instance. Perform the following steps to register the media assets:
- Create a replica set instance that consists of three nodes and provides a low specification. For more information, see Create a replica set instance.
- Migrate the data in your standalone instance to the new replica set instance. For more information, see Overview.
- Verify that the new replica set instance runs as expected. Then, switch the workloads in your standalone instance over to the new replica set instance.
- Optional:If you no longer need your standalone instance, use one of the following methods to release the instance:
- For a subscription instance, you cannot manually release the instance.
- For a pay-as-you-go instance, you can manually release the instance. For more information, see Release an instance or a node.