tencent cloud


Enabling Database Proxy

Last updated: 2022-08-31 15:06:40

    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 (except Zones 1, 2, and 4), Shanghai (except Zone 1), Guangzhou (except Zones 1 and 2), 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 (the kernel minor version should be 20201230 or later), and two-node and three-node MySQL 8.0 (the kernel minor version should be 20211130 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.


    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, select the specification and node quantity, click OK, and refresh.
      • Network: Only VPC is supported currently. The VPC of the source instance is selected by default.
      • Proxy Specification: 2-core 4000 MB memory, 4-core 8000 MB memory, or 8-core 16000 MB memory.
      • 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.
      • Connection Pool Status: For more information, see Connection Pool Overview.
      • Security Group: It is an important means of network security isolation. You can choose an existing security group or create a new one as needed.
    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 database proxy address and network type and add remarks in the Connection Address section.

      • 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. Make sure that your business has a reconnection mechanism.
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support