The Cloud SQLService Level Agreement (SLA) excludes outages "caused by factors outsideof Google’s reasonable control". This page describes some of the user-controlledconfigurations that can cause an outage for a Cloud SQL instance to beexcluded.

Introduction

Cloud SQL strives to give you as much control over how your instance isconfigured as possible. This includes some configurations that increase the riskof instance downtime, depending on the load and other configuration parameters.If your instance becomes unhealthy, and Cloud SQL determines that it was out ofcompliance with the operational limits as described on this page, then thedowntime period is not covered by (or does not count against) theCloud SQLSLA.

This list of operational limits is presented to inform you which configurationspresent these risks, ways to avoid theseconfigurations, and ways to mitigate the risks when the configuration isrequired for your business environment.

Note: You are responsible for monitoring your instance to ensure that itis properly sized and configured for the size and type of load it isexperiencing.

Excluded configurations

The excluded configurations fall into the following categories:

• General configuration requirements
• Database flag values
• Resource constraints

General configuration requirements

Only Cloud SQL instances configured for high availability with at least onededicated CPU are covered by the Cloud SQLSLA. Shared-core instances and single-zoneinstances are not covered by the SLA.

If the instance is configured and used in a way that causes the workloadto overload the instance or the instance to experience a long recovery time,then the SLA does not apply.

We strongly advise you to set up alerts and monitoringinCloud Monitoring.

Database flag values

Cloud SQL lets you configure your instance usingdatabaseflags. Some of these flags, such asautovacuumandmax_wal_size, can be set in ways that might compromise thestability of the instance or the durability of its data.

For a complete list of configurable flags and their defaults,seedatabase flags.

Resource constraints

The following resource constraints must be avoided to retain SLA coverage:

• Storage full: if your disk utilization is consistently high, and automaticstorage increase is not enabled, your instance is not properly sized for yourworkload and may not be covered by theSLA.
• CPU overloaded: if your CPU utilization is consistently high, yourinstance is not properly sized for your workload, and may not be covered bytheSLA.
• Memory overloaded: if your memory usage is consistently high, your instanceis not properly sized for your workload, and may not be covered by theSLA.
• Transaction ID wraparound: if your instance runs out of transaction ID and goesoffline, this outage is not covered by theSLA.

For more information, refer to theGeneral best practices.