RDS for MySQL
RDS for MySQL
RDS for MySQL
Document
What's new
Announcement
Product introduction
Product billing
Billing method
Kernel functions
Feature
Stability
Performance
Quick start
User guide
Managing instances
Changing an instance configuration
Upgrading kernel versions
Managing tags
Managing disaster instances
Managing blue-green deployment
Migrating data
Managing connections
Database proxy
Connecting to an instance
Managing connection endpoints
Diagnosing connections
Managing connection pool modes
Managing access addresses and ports
Managing databases
Account and access authorization
Backup recovery
Backup data
Data recovery
Service availability
Managing logs
Managing data security
Managing allowlists
Configuring SSL encryption
Managing parameters
Monitoring and alerts
Task center
Operation and maintenance events
Backups of deleted instances
Managing cross-regional backups
API reference
V2（2022-01-01）
Global management
Managing instances
Managing connections
Managing accounts
Managing databases
Security encryption
Backup and recovery
Managing parameters
Managing tasks
Event management
Managing logs
Resource plan management
Appendix
SDK reference
Developer tools
Best practice
Performance document
Troubleshooting
- Documentation
RDS for MySQLUser guideManaging connectionsManaging connection endpointsEnabling or disabling transaction splitting
Copy page
Download PDFManaging connection endpoints
Enabling or disabling transaction splitting
Copy pageDownload PDFEnabling or disabling transaction splitting
By default, the database proxy sends all requests in a transaction to the primary node to ensure transaction correctness. However, some frameworks encapsulate all requests into non-autocommit transactions (by disabling autocommit with set autocommit=0;), which overloads the primary node. To address this, RDS for MySQL provides a transaction splitting feature. This feature splits requests within a transaction by routing read requests that occur before the first write request to a read-only or secondary node, reducing the load on the primary node.
Precautions
- Only proxy endpoints in Read/Write mode support transaction splitting.
- Only implicit transaction splitting is supported for transactions where autocommit=0.
Required
- An instance has been created and the instance state is Running. For more details, refer to Create instance.
- The database proxy is enabled for the instance, and a connection endpoint in Read/Write mode has been created. For details about enabling the database proxy and creating a connection endpoint, refer to Enable database proxy and Create endpoint.
Procedure
- Log on to the RDS for MySQL console.
- In the upper-left corner of the top menu bar, select the project and region for the instance.
tip
If the project to which the instance belongs is not set, this operation should select the project as All resources.
- In the left navigation bar, choose MySQL \> Instance list.
- On the Instances page, click the target instance name.
- At the top of the page, click the Connectivity tab.
- On the Connectivity page, in the Endpoints list, click Edit in the Actions column for the target connection endpoint to open the Modify endpoint page.
- On the Modify endpoint page, enable or disable transaction splitting, and then click OK.
Last updated: 2025.09.28 17:04:32
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
