Parameter | Description |
Network | Database proxy only supports VPC. You can choose to automatically assign or specify an address. |
Security group | The security group of the source instance is selected by default. You can also select another or more existing security groups 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. You can add remarks for the new database proxy connection address. |
Parameter | Description |
Read-Write Attribute | Select 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. |
Was this page helpful?