：Modify proxy terminal settings

The operation that you want to perform. Set the value to ModifyDBProxyEndpoint.

The ID of the instance. You can call the DescribeDBInstances operation to query the ID of the instance.

The ID of the proxy endpoint. You can call the DescribeDBProxyEndpoint operation to query the ID of the proxy endpoint.

The features that you want to enable for the proxy endpoint. If you specify more than one feature, separate the features with semicolons (;). Format: Feature 1:Status;Feature 2:Status;.... Do not add a semicolon (;) at the end of the last value.

Valid feature values:

• ReadWriteSpliting: read/write splitting
• ConnectionPersist: connection pooling
• TransactionReadSqlRouteOptimizeStatus: transaction splitting

Valid status values:

• 1: enabled
• 0: disabled

The region ID of the instance. You can call the DescribeRegions operation to query the most recent region list.

The maximum latency threshold that is allowed for read/write splitting. If the latency on a read-only instance exceeds the threshold that you specified, ApsaraDB RDS no longer forwards read requests to the read-only instance. If you do not specify this parameter, the original value of this parameter is retained. Unit: seconds. Valid values: 30 to 3600. Default value: 30.

The policy that is used to allocate read weights. Valid values:

• Standard: ApsaraDB RDS automatically allocates read weights to the instance and its read-only instances based on the specifications of the instances.
• Custom: You must manually allocate read weights to the instance and its read-only instances.

For more information about the permission allocation policy, see Modify the latency threshold and read weights of ApsaraDB RDS for MySQL instances and Enable and configure the database proxy feature for an ApsaraDB RDS for PostgreSQL instance.

The read weights of the instance and its read-only instances. A read weight must be a multiple of 100 and cannot exceed 10000. Formats:

• Standard instance: {"ID of the primary instance":"Weight","ID of the read-only instance":"Weight"...}

  Example: {"rm-uf6wjk5xxxx":"500","rr-tfhfgk5xxx":"200"...}

• Cluster instance: {"ID of the read-only instance ID":"Weight","DBClusterNode":{"ID of the primary node":"Weight","ID of the secondary node ID":"Weight","ID of the secondary node ID":"Weight"...}}

  Example: {"rr-tfhfgk5xxx":"200","DBClusterNode":{"rn-2z****":"0","rn-2z****":"400","rn-2z****":"400"...}}

  Note The DBClusterNode parameter is required if the instance runs RDS Cluster Edition. The DBClusterNode parameter includes information about IDs and weights of the primary and secondary nodes.

The type of the operation that you want to perform. Valid values:

• Modify: Modify a proxy terminal. This is the default value.
• Create: Create a proxy terminal.
• Delete: Delete a proxy terminal.

The description of the proxy terminal.

The type of the proxy terminal. This is a reserved parameter. You do not need to specify this parameter.

The read and write attributes of the proxy terminal. Valid values:

• ReadWrite: The proxy terminal connects to the primary instance and can receive both read and write requests.
• ReadOnly: The proxy terminal does not connect to the primary instance and can receive only read requests. This is the default value.

An internal parameter. You do not need to specify this parameter.

The ID of the request.