This document describes how to enable database proxy in the TencentDB for MySQL console.
Database proxy is a network proxy service between the TencentDB service and the application service. It is used to proxy all requests when the application service accesses the database. It provides advanced features such as automatic read/write separation, connection pool, and connection persistence and boasts high availability, high performance, Ops support, and ease of use.
Prerequisite
The instance is running on the two-node or three-node architecture.
Note
Database proxy currently is supported in the following regions:
Beijing (except Zones 1, 2, and 4), Shanghai (except Zone 1), Guangzhou (except Zones 1 and 2), Shanghai Finance (except Zones 1 and 2), Beijing Finance, Chengdu, Chongqing, Nanjing, and Hong Kong (China) (except Zone 1).
Tokyo (except Zone 1), Bangkok (except Zone 1), Virginia (except Zone 1), Silicon Valley (except Zone 1), Mumbai (except Zone 1), Seoul (except Zone 1), and Singapore (except Zones 1 and 2).
Database proxy currently is supported on the following versions: two-node and three-node MySQL 5.7 (with kernel minor version 20211030 or later) and three-node MySQL 8.0 (with kernel minor version 20211202 or later). If you upgrade the kernel minor version of the source instance, the associated read-only and disaster recovery instances will be upgraded at the same time. For more information, see Upgrading Kernel Minor Version. Directions
1. Log in to the TencentDB for MySQL console. In the instance list, select the source instance for which to enable database proxy and click its ID or Manage in the Operation column to enter the instance management page. 2. On the instance management page, select the Database Proxy tab and click Enable Now.
3. In the pop-up window, configure the following items and click OK.
|
Network | Select the network of the database proxy, which can only be a VPC. |
Proxy Specification | Select 2-core 4000 MB memory, 4-core 8000 MB memory, or 8-core 16000 MB memory. |
AZ and Node Quantity | 1. Select the database proxy AZ. You can click Add AZ to add more AZs. The number of selectable AZs depends on how many AZs are available in the current region. You can select up to three AZs. 2. Select the number of nodes. We recommend that you set the quantity to 1/8 (rounded up) of the total number of CPU cores on the source and read-only instances; for example, if the source instance has 4 CPU cores, and the read-only instance has 8 CPU cores, then the recommended node quantity will be (4 + 8) / 8 ≈ 2. Note If the selected proxy and the source instance are not in the same AZ and you access the instance through the proxy, the write performance may be reduced.
If the recommended number of proxy nodes you calculated exceeds the maximum purchasable quantity, choose a higher proxy node specification.
|
Security group | The security group of the source instance is selected by default. You can also select another existing security group or create a new one as needed. Note To access through the database proxy, you need to configure security group policies and open the private port (3306).
For more information, see TencentDB Security Group Management.
|
Remarks | (Optional) Enter the remarks of the database proxy service to be enabled. |
4. After successfully enabling the service, you can manage proxy nodes and view their basic information on the database proxy page. You can also modify the access address, network type, and remarks of the database proxy, view and adjust the connection configuration, and perform rebalance in the Connection Address section.
Note
You can view Connections in the proxy node list or view the performance monitoring data of each proxy node to check whether the numbers of connections on the nodes are unbalanced, and if so, you can distribute the connections by clicking Rebalance.
Rebalance will cause proxy nodes to restart, and the service will become unavailable momentarily during the restart. We recommend that you restart the service during off-peak hours. Make sure that your business has a reconnection mechanism.
Was this page helpful?