Cloud DB for MySQL troubleshooting

Prev Next

Available in Classic and VPC

This page lists problems you might run into when using Cloud DB for MySQL Click on the error to see more details.

Troubleshoot common issues

The following are examples of common errors you might encounter:

Individual start and stop of MySQL Server
Unable to start and stop MySQL Server individually.

MySQL Server connection error
Error occurs when accessing the MySQL Server.
Currently using SSL VPN but cannot connect to Cloud DB for MySQL.

Failover when restarting Master Server
Failover not executed when restarting Master Server.

Execute Failover
You need to reproduce a Master Server failover situation prior to service launch to proactively verify that applications remain unaffected during such incidents.

Deleted data recovery
Recovery of deleted data is needed.

Create database
Direct database creation is needed.

Notifications on exceeding MySQL Server threshold
Unable to receive an event notification on exceeding MySQL Server threshold.

Replication error
Replication error occurs and replication stopped.

Mitigate Replication delay
Replication delay occurs.

Troubleshoot usage and performance issues

The following are examples of resource errors you might encounter:

Data storage size decreased after restarting MySQL Server (VPC)
The size of data storage decreased after restarting MySQL Server.

Data storage size decreased after restarting MySQL Server (Classic)
The size of data storage decreased after restarting MySQL Server.

Memory usage increased
Memory usage keeps increasing.

DB performance issues and response delays
Issue in DB performance occurs.
There is a delay in DB response.

High CPU usage
CPU usage is high.

Learning resources

We offer various materials for you to explore. To learn more about Cloud DB for MySQL, check out these helpful links:

Note

If you're still having trouble finding what you need, click on the feedback icon and send us your thoughts and requests. We'll use your feedback to improve this guide.