Supports Implementing Read-write Splitting on Transactions
Nov 29 2019
The transaction splitting feature splits read requests from transactions and forwards these requests to read-only nodes without compromising session consistency. This helps to reduce the workloads on the primary node.
Content
Target customers: ApsaraDB POLARDB for MySQL users if their workloads running on the primary node are higher than those running on the read-only nodes. Features released: the transaction splitting option is added for the cluster endpoint configuration in the console. You can either enable or disable transaction splitting. By default, this feature is enabled for newly purchased clusters and disabled for existing clusters. You can enable this feature on existing clusters on the fly. No reboot is required.
