In order to provide better service, higher performance, and lower network latency, the TencentDB for MySQL team has fully upgraded the private network access linkage.
Note:
- The new architecture will deliver higher performance and network stability and lower network latency. For more information, see Network Architecture Performance Comparison.
- A momentary disconnection from the database may occur during the architecture upgrade. Make sure that your business has a reconnection mechanism.
- Single-node instances of cloud disk edition are already in the optimal network architecture, so their details page does not indicate whether the network architecture is new. This upgrade will not involve such instances.
- The new network architecture cannot be used in the classic network, so the new architecture flag will not be displayed for it. To use it, switch to VPC as instructed in Network Switch.
You can view the network architecture upgrade progress of the current instance through the flag after Basic Info > Private Network Address on the instance details page in the console.
If the flag is Not upgraded, the current instance has not been scheduled for the network architecture upgrade. We recommend you wait patiently.
If the flag is To be upgraded, the current instance will undergo the network architecture upgrade during the maintenance time. You can adjust the maintenance time to change the upgrade time. If the instance has other tasks to be performed during the maintenance time, the upgrade will be postponed to the next maintenance time. We will send you an upgrade notification in the Message Center about one week before the upgrade.
If the flag is New architecture, the current instance has already been upgraded to the new architecture.
Thank you for your support!
Was this page helpful?