tencent cloud

After database proxy is enabled for TencentDB for MySQL, a database proxy connection address will be added by default. You can also add connection addresses later to implement different business logics. The number of connection addresses that can be created is the same as that of database proxy nodes. You can view and modify the access policy of a connection address in the console.

Prerequisites

You have enabled the database proxy. For more information, see Enabling Database Proxy.

Viewing the access policy

1. Log in to the TencentDB for MySQL console, select the region at the top of the page, and click the ID of the target instance to enter the instance management page.
2. On the instance management page, select Database Proxy > Access Policy.
   

Modifying the access policy

1. Log in to the TencentDB for MySQL console, select the region at the top of the page, and click the ID of the target instance to enter the instance management page.
2. On the instance management page, select Database Proxy > Access Policy, find the target access policy, and click Settings.

   Note：

   You can also find the target access address in Database Proxy > Overview > Connection Address. Then, click Adjust Configurations in the Operation column.

3. In the pop-up window, modify the policy configuration and click OK.
   

   Parameter	Description
   Read-Write Attribute	Modify the read-write attribute of the proxy access address, which can be **Read/Write Separation** or **Read-Only**.
   Remove Delayed RO Instances	Set the **Remove Delayed RO Instances** policy. After this option is enabled, you can set **Delay Threshold** and **Least RO Instances**. The system will try removing or restoring a failed read-only instance no matter whether this option is enabled. **Delay Threshold**: Enter an integer greater than or equal to 1 (in seconds). **Least RO Instances**: It is subject to the number of read-only instances owned by the source instance. If it is set to `0`, when all read-only nodes are removed, all read requests will be routed to the source instance until at least one of the removed read-only instances rejoins the database proxy to continue processing the read requests.
   Connection Pool Status	The connection pool feature mainly mitigates the instance load caused by frequent new connections in non-persistent connection business scenarios. After this option is enabled, you can select the supported connection pool type, which currently can only be the session-level connection pool by default.
   Transaction Split	You can set whether to enable this feature. After it is enabled, reads and writes in one transaction will be separated to different instances for execution, and read requests will be forwarded to read-only instances to reduce the load of the source instance.
   Assign Read Weight	You can select **Assigned by system** or **Custom**. If multiple AZs are configured when the database proxy is enabled, you can separately assign the weights of proxy nodes in different AZs.
   Failover (with **Read-Write Attribute** being **Read/Write Separation**)	You can set whether to enable this feature. After it is enabled, if database proxy fails, the database proxy address will route requests to the source instance.
   Apply to Newly Added RO Instances	You can set whether to enable this feature. After it is enabled, a newly purchased read-only instance will be automatically added to the database proxy. If **Assign Read Weight** is set to **Assigned by system**, newly purchased read-only instances will be assigned with the default weight based on their specification. If **Assign Read Weight** is set to **Custom**, when newly purchased read-only instances are added, their weights will be 0 by default, which can be modified by clicking **Adjust Configurations** in **Connection Address** on the **Database Proxy** tab.