This page lists known issues with Cloud SQL for MySQL, along with ways you can avoid or recover from these issues.If you are experiencing issues with your instance, make sure you also review the Operational Guidelines, as well as the information in Diagnosing Issues.
Data durability and availability issues
Generated columns (MySQL 5.7 instances only)
Due to an issue in MySQL, using generated columns might result in data corruption. For more information, see MySQL bug #82736.
Instance connection issues
Expired SSL/TLS certificates
If your instance is configured to use SSL, go to the Cloud SQL Instances page in the Cloud Console and open the instance. Open its Connections page and make sure that your server certificate is valid. If it has expired, you must add a new certificate and rotate to it. Learn more.
Cloud SQL Auth proxy version
If you are connecting using the Cloud SQL Auth proxy, make sure you are using the most recent version. For more information, see Keeping the Cloud SQL Auth proxy up to date.
Not authorized to connect
If you try to connect to an instance that does not exist in that project, the error message only says that you are not authorized to access that instance.
Long-running Cloud SQL instance operations cannot be cancelled or stopped
When you start a long-running Cloud SQL instance operation, such as an import or export operation, you cannot stop the operation before it completes. In addition, only one operation can run against an instance at at time.
For this reason, make sure you do not need to do other work on an instance when you start a long-running operation.
Instance names cannot be reused immediately after instance deletion
After you delete an instance, you cannot immediately reuse the instance name, because Cloud SQL reserves that name for a few days. If you need to create and delete instances with the same name, consider using a timestamp as part of the name to avoid name conflicts.
Setting the time zone for MySQL instances
It is possible to set the MySQL time zone to a named area, such as "Europe/Moscow", using a session variable. However, doing so is not supported in Cloud SQL, and is not guaranteed to provide up-to-date time settings. To change the default time zone for your instance, update the
default_time_zoneflag with the offset from UTC (for example,
+10:00). Automatic adjustment to daylight savings time is not supported; you must update the
default_time_zoneflag manually to account for daylight savings time.
Issues with importing and exporting data
CSV export does not format NULLs and newlines correctly
When you export data as CSV using the Cloud SQL export feature, NULLs are exported as
"N, which can cause the CSV file to contain unbalanced quotation marks. Additionally, if your text data contains a newline character, a trailing quote mark is added at the end of the line.
The SQL Mode setting affects how Cloud SQL interprets SQL queries.
For example, if you export from a database without Strict SQL enabled, then try to import to Cloud SQL (which enables Strict SQL by default), the import might fail. The best practice is to use the same SQL Mode on import that you used for export.
The DEFINER clause may cause import to fail
A DEFINER clause may cause an import operation to fail if the DEFINER user is a SUPER or system user and is different from the user doing the import into Cloud SQL. Learn more about DEFINER usage and potential workarounds in Cloud SQL.
Transaction logs and disk growth
Logs are purged once daily, not continuously. When the number of days of log retention is configured to be the same as the number of backups, a day of logging might be lost, depending on when the backup occurs. For example, setting log retention to seven days and backup retention to seven backups means that between six and seven days of logs will be retained.
We recommend setting the number of backups to at least one more than the days of log retention to guarantee a minimum of specified days of log retention.