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.
- Database proxy currently is supported in the following regions: Beijing, Shanghai, and Guangzhou.
- Database proxy currently is supported on the following versions: two-node and three-node MySQL v5.7 (the kernel minor version should be 20201230 or above). 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, please see Upgrading Kernel Minor Version.
- 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.
- On the instance management page, select the Database Proxy tab and click Enable Now.
- In the pop-up window, select the specification and node quantity and click OK.
- Network: currently, only VPC is supported. The VPC of the source instance is selected by default.
- Proxy Specification: currently, only one specification is supported.
- Node Quantity: number of proxy nodes. We recommend 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.
- After successfully enabling the service, you can manage proxy nodes and view their basic information on the database proxy page.
- 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 you restart the service during off-peak hours. Please make sure that your business has a reconnection mechanism.