Relational Database ServiceRelational Database Service

Compute
Elastic Cloud Server
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
Domain Name Service
VPC Endpoint
Cloud Connect
Enterprise Switch
Security & Compliance
Anti-DDoS
Web Application Firewall
Host Security Service
Data Encryption Workshop
Database Security Service
Advanced Anti-DDoS
Data Security Center
Container Guard Service
Situation Awareness
Managed Threat Detection
Compass
Cloud Certificate Manager
Anti-DDoS Service
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GaussDB NoSQL
GaussDB(for MySQL)
Distributed Database Middleware
GaussDB(for openGauss)
Developer Services
ServiceStage
Distributed Cache Service
Simple Message Notification
Application Performance Management
Application Operations Management
Blockchain Service
API Gateway
Cloud Performance Test Service
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
DevCloud
ProjectMan
CodeHub
CloudRelease
CloudPipeline
CloudBuild
CloudDeploy
Cloud Communications
Message & SMS
Cloud Ecosystem
Marketplace
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP License Service
Support Plans
Customer Operation Capabilities
Partner Support Plans
Professional Services
enterprise-collaboration
Meeting
IoT
IoT
Intelligent EdgeFabric
DeveloperTools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Updated at: Apr 02, 2022 GMT+08:00

Suggestions on Using Database Proxy

rdsProxy is an internal database proxy account for RDS. To ensure the proper running of read/write splitting, you are advised not to create an account with the same name as rdsProxy.

Function Constraints

  • After read/write splitting is enabled, if you delete a primary RDS for MySQL instance, the read replicas are also deleted and the read/write splitting function is disabled.
  • Read/write splitting does not support the caching_sha2_password identity authentication plugin for RDS for MySQL 8.0.
  • After read/write splitting is enabled, the database ports, security groups, and floating IP addresses of both the primary instance and read replicas cannot be changed.
  • Read/write splitting does not support SSL.
  • Read/write splitting does not support compression protocols.
  • Read/write splitting does not support the isolation level READ UNCOMMITTED.
  • If multi-statements are executed, all subsequent requests will be routed to the primary instance. To restore the read/write splitting, disconnect the connection between your application and the read/write splitting address and establish a connection again.
  • When the read/write splitting address is used, all transaction requests are routed to the primary instance (you can use the transaction splitting feature to route read requests prior to write operations in a transaction to read replicas). The non-transaction read consistency is not ensured. To ensure read consistency, encapsulate the read requests into a transaction.
  • When the read/write splitting address is used, the LAST_INSERT_ID() function can be used only in transactions.

Syntax Constraints

Read/write splitting routes frontend requests to backend instance nodes by the configured weights.

Therefore, some SQL statements may have different results when being executed multiple times.

  • When the read/write splitting address is used, the execution results of the show processlist command are inconsistent.
  • When the read/write splitting address is used, the kill query operation is not supported.
  • When the read/write splitting address is used, the show errors and show warnings commands are not supported.
  • When the read/write splitting address is used, user-defined variables, such as the SET @variable statements, are not supported.
  • When the read/write splitting address is used, if stored procedures and functions depend on user variables (@variable), the execution result may be incorrect.

Did you find this page helpful?

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel