TDSQL-C for MySQL
- Release Notes and Announcements
- Announcements
- Product Introduction
- Suggestions on Usage Specifications
- Kernel Features
- Kernel Version Release Notes
- Optimized Kernel Version
- Functionality Features
- Performance Features
- Security Features
- Stability Feature
- Analysis Engine Features
- Purchase Guide
- Value-Added Services Billing Overview
- Database Audit
- Audit Rule Template
- Serverless Service
- Serverless Introduction
- Serverless Resource Pack
- Configuration Change
- Operation Guide
- Database Connection
- Configuring Network Address
- Instance Management
- Configuration Adjustment
- Instance Mode Management
- Cluster Management
- Scaling Instance
- Database Proxy
- Database Proxy Kernel Features
- Managing Database Proxy
- Automatic Read/Write Separation
- Connection Pool Feature
- Other Features
- Account Management
- Console Account
- Database Account
- Configuring Custom Password Strength
- Database Management
- Database Management Tool
- Columnar Storage Index (CSI)
- Utilization of Columnar Storage Indexes
- Read-Only Analysis Engine
- Feature Limits and Compatibility
- Description of Functions and Operators
- Read-Only Analysis Engine Management
- Data Loading
- Executing Queries
- Exclusive Features
- Performance Optimization
- Performance White Paper
- Parameter Configuration
- Multi-AZ Deployment
- Backup and Restoration
- Performing Backup
- Managing Backup
- Rollback
- Restoring Data from Logical Backups
- Restoring Data Through the Console
- Restoring Data from Snapshot Backup
- Data Migration
- Parallel Query
- Setting Parallel Query
- Database Security and Encryption
- Access and Authorization
- Security Group Management
- TencentDB Security Group Management
- Monitoring and Alarms
- Monitoring
- Alarms
- Monitoring Metric Alarm
- Practical Tutorial
- Data Rollback
- Database/Table-Level Rollback
- Rolling back Entire Cluster
- White Paper
- Security White Paper
- Performance White Paper
- Troubleshooting
- Connection Issues
- API Documentation
- Making API Requests
- Instance APIs
- Account APIs
- Audit APIs
- Database Proxy APIs
- Backup and Restoration APIs
- Parameter Management APIs
- Performance Analysis APIs
- Serverless APIs
- ResourcePackage APIs
- Other APIs
- FAQs
- Service Agreement
- TDSQL-C Policy
- General References
DocumentationTDSQL-C for MySQLOperation GuideDatabase ProxyManaging Database ProxyAdjusting Database Proxy Configuration
Adjusting Database Proxy Configuration
Last updated: 2024-03-07 10:27:16
You can adjust the specification and node count of the database proxy in the console.
Prerequisite
Notes
The database proxy will be automatically upgraded to the latest version during configuration adjustment if its version is old.
If the selected database proxy does not reside in the same availability zone with the primary instance, a potential decline in write performance may be observed during the connection via the database proxy.
If the required number of proxy nodes exceed the purchase limit upon calculation, it is advisable to choose a higher specification proxy.
When the proxy specification is 2 cores and 4000MB of memory, the recommended number of proxies is 1/8th (rounded up) of the sum of the CPU core numbers of the main instance and the read-only instance.
When the proxy specification is 4 cores and 8000MB of memory, the recommended number of proxies is 1/16th (rounded up) of the sum of the CPU core numbers of the main instance and the read-only instance.
When the proxy specification is 8 cores and 16000MB of memory, the recommended number of proxies is 1/32 (rounded up) of the sum of the CPU core numbers of the main instance and the read-only instance.
Impact Description
Changing different configuration items has different impacts, certain modifications will not result in connection interruptions, while others may cause such disruptions. The specific changeable items and their corresponding impacts are detailed in the following table.
Scenario One: Changed Proxy Specification and Unchanged Availability Zone and Node Count
Proxy Specification | Availability Zone | Number of Nodes | Switch Time | Impact |
Upgrade or downgrade | Unchanged | Unchanged | During the maintenance period | There may be momentary interruptions. Please ensure your operations are equipped with a reconnection mechanism. |
| | | | Upon completion of the upgrade |
Scenario Two: Changed Node Count and Unchanged Proxy Specification and Availability Zone
Proxy Specification | Availability Zone | Number of Nodes | Load Balancing Method | Switch Time | Impact |
Unchanged | Unchanged | Raised | Automatic | During the maintenance period | There may be momentary interruptions. Please ensure your operations are equipped with a reconnection mechanism. |
| | | | | Upon completion of the upgrade |
| | | Manual | During the maintenance period | It will not result in intermittent interruptions. |
| | | | | Upon completion of the upgrade |
| | Reduced | Automatic | During the maintenance period | Momentary interruptions may occur. Please ensure your operations are equipped with a reconnection mechanism. |
| | | | | Upon completion of the upgrade |
| | | | Manual | During the maintenance period |
| | | | | Upon completion of the upgrade |
Scenario Three: Unchanged Proxy Specification and Availability Zone and Node Count Combination Changed
Proxy Specification | Availability Zone | Number of Nodes | Load Balancing Method | Switch Time | Impact |
Unchanged | Raised | Raised | Automatic | During the maintenance period | There may be momentary interruptions. Please ensure your operations are equipped with a reconnection mechanism. |
| | | | | Upon completion of the upgrade |
| | | Manual | During the maintenance period | It will not result in intermittent interruptions. |
| | | | | Upon completion of the upgrade |
| | Reduced | Automatic | During the maintenance period | Momentary interruptions may occur. Please ensure your business is equipped with a reconnection mechanism. |
| | | | | Upon completion of the upgrade |
| | | | Manual | During the maintenance period |
| | | | | Upon completion of the upgrade |
| | Reduced | Raised | Automatic | During the maintenance period |
| | | | | Upon completion of the upgrade |
| | | | Manual | During the maintenance period |
| | | | | Upon completion of the upgrade |
| | | Reduced | Automatic | During the maintenance period |
| | | | | Upon completion of the upgrade |
| | | | Manual | During the maintenance period |
| | | | | Upon completion of the upgrade |
| | Changed | Raised | Automatic | During the maintenance period |
| | | | | Upon completion of the upgrade |
| | | | Manual | During the maintenance period |
| | | | | Upon completion of the upgrade |
| | | Reduced | Automatic | During the maintenance period |
| | | | | Upon completion of the upgrade |
| | | | Manual | During the maintenance period |
| | | | | Upon completion of the upgrade |
Directions
1. Log in to the TDSQL-C for MySQL console. In the cluster list, select the cluster with the proxy enabled, click on the cluster ID, and proceed to the cluster management page.
2. Navigate to the Cluster Management page > Cluster Details > Database Proxy, and click Details, or directly select the Database Proxy tab on the Cluster Management page to access the Database Proxy Management page.
3. On the Overview tab on the Database Proxy tab, Click Adjust Configuration after Basic Information > Number of Nodes. The output content is in markdown format.
4. In the pop-up window, modify the relevant configurations of the database proxy (proxy specification, availability zone, and number of nodes) as needed, then click Confirm.
5. In Basic Info on the Database Proxy tab, after the task status changes from Upgrading to Running/Waiting to upgrade, the configuration adjustment is completed.
Note:
If you select Upon upgrade completion, after the configuration is adjusted, the system will automatically switch to the new configuration.
If you select During maintenance time, after the configuration is adjusted, the system will switch the configuration during the specified maintenance time period.
If you select During maintenance time but need to switch the configuration earlier due to your business requirements, after the configuration is adjusted, you can go to Database Proxy > Overview > Basic Info > Status/Task and click Execute now next to Running/Waiting to upgrade.
If the CLB resettings are performed manually after configuration adjustment, once the configuration adjustment is complete, one can manually perform CLB resettings under the corresponding Overview > Connection Address on the database proxy page.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No