Cloud DB for MySQL troubleshooting

Available in Classic and VPC

Learn how to resolve issues with Cloud DB for MySQL. Click any error for detailed troubleshooting steps.

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.

mysqldump utility error
An error occurs when performing a backup or restore using the mysqldump utility.

Unknown status
The server status is displayed as Unknown.

Unsupported engine table creation restriction
Tables using the MyISAM, BLACKHOLE, FEDERATED, ARCHIVE, or MEMORY engine cannot be created.

Error notifications in the console
The following error notifications occur in the console.

• CASE 1: MySQL replication is in a delayed state. Try again after all delays have been resolved.
• CASE 2: Master DB failover cannot be performed due to unstable communication with the DB server. Try again after a short while.
• CASE 3: Work cannot be performed before or after the backup time. To proceed with the work, adjust the backup time.
• CASE 4: A backup is currently in progress. Proceed with the work after the backup has been completed. The backup duration increases in proportion to the size of user data.

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:

• FAQs: Get answers to common Cloud DB for MySQL questions
• NAVER Cloud Platform blog: MySQL major version upgrade (MySQL 5 → MySQL 8) — NAVER Cloud Platform Cloud DB for MySQL practice
• NAVER Cloud Platform blog: Data migration from Cloud DB for MySQL to Cloud Hadoop with Sqoop
• NAVER Cloud Platform blog: Deliver APIs without an application server using Cloud Functions service and Cloud DB_Part 1
• NAVER Cloud Platform blog: Deliver APIs without an application server using Cloud Functions service and Cloud DB_Part 2