Cloud SQL은 인스턴스 구성 방법을 사용자가 최대한 제어할 수 있도록 하기 위해 노력하고 있습니다. 여기에는 부하 및 기타 구성 매개변수에 따라 인스턴스 다운타임의 위험을 증가시킬 수 있는 몇 가지 구성이 포함됩니다.
인스턴스가 비정상 상태가 되는 경우 Cloud SQL에서 확인한 결과, 이 페이지에 설명한 작업 제한을 준수하지 않아 중단되었다고 판단될 경우 다운타임 기간에 Cloud SQL SLA가 적용되지 않습니다(또는 계산에 포함되지 않음).
이 작업 제한 목록은 위와 같은 위험을 야기하는 구성, 이러한 구성을 방지하는 방법, 비즈니스 환경에 따라 그러한 구성이 꼭 필요할 경우 위험을 완화하는 방법을 알려주기 위한 것입니다.
제외되는 구성
제외되는 구성은 다음과 같은 카테고리로 분류됩니다.
일반적인 구성 요구사항
데이터베이스 플래그 값
리소스 제약조건
일반적인 구성 요구사항
하나 이상의 전용 CPU와 함께 고가용성으로 구성된 Cloud SQL 인스턴스만 SLA의 적용을 받습니다. 공유 코어 인스턴스와 단일 영역 인스턴스에는 SLA가 적용되지 않습니다.
인스턴스가 구성되고 워크로드가 인스턴스에 과부하를 초래하는 방식으로 사용되거나 인스턴스의 복구 시간이 길어질 경우 SLA가 적용되지 않습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[],[],null,["# Operational guidelines\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nThe Cloud SQL [Service Level Agreement (SLA)](/sql/sla) excludes outages \"caused by factors outside\nof Google's reasonable control\". This page describes some of the user-controlled\nconfigurations that can cause an outage for a Cloud SQL instance to be\nexcluded.\n\nFor Cloud SQL engine-specific configurations, see the following pages\nfor engine-specific operational guidelines:\n\n- [Cloud SQL for MySQL operational guidelines](/sql/docs/mysql/operational-guidelines)\n- [Cloud SQL for PostgreSQL operational guidelines](/sql/docs/postgres/operational-guidelines)\n- [Cloud SQL for SQL Server operational guidelines](/sql/docs/sqlserver/operational-guidelines)\n\nIntroduction\n------------\n\nCloud SQL strives to give you as much control over how your instance is\nconfigured as possible. This includes some configurations that increase the risk\nof instance downtime, depending on the load and other configuration parameters.\nIf your instance becomes unhealthy, and Cloud SQL determines that it was out of\ncompliance with the operational limits as described on this page, then the\ndowntime period is not covered by (or does not count against) the\nCloud SQL [SLA](/sql/sla).\n\nThis list of operational limits is presented to inform you which configurations\npresent these risks, ways to avoid these\nconfigurations, and ways to mitigate the risks when the configuration is\nrequired for your business environment.\n| **Note:** You are responsible for monitoring your instance to ensure that it is properly sized and configured for the size and type of load it is experiencing.\n\nExcluded configurations\n-----------------------\n\nThe excluded configurations fall into the following categories:\n\n- General configuration requirements\n- Database flag values\n- Resource constraints\n\n### General configuration requirements\n\nOnly Cloud SQL instances configured for high availability with at least one\ndedicated CPU are covered by the Cloud SQL [SLA](/sql/sla). Shared-core instances and single-zone\ninstances are not covered by the SLA.\n\nIf the instance is configured and used in a way that causes the workload\nto overload the instance or the instance to experience a long recovery time,\nthen the SLA does not apply.\n\nWe strongly advise you to set up alerts and monitoring\nin [Cloud Monitoring](/sql/docs/mysql/monitor-instance).\n\n### Database flag values\n\nCloud SQL lets you configure your instance using [database\nflags](/sql/docs/mysql/flags). Some of these flags can be set in ways that might compromise the\nstability of the instance or the durability of its data.\n\nFor Cloud SQL engine-specific configurations, see the following pages for\nengine-specific flags:\n\n- [Cloud SQL for MySQL database flags](/sql/docs/mysql/flags)\n- [Cloud SQL for PostgreSQL database flags](/sql/docs/postgres/flags)\n- [Cloud SQL for SQL Server database flags](/sql/docs/sqlserver/flags)\n\n### Resource constraints\n\nThe following resource constraints must be avoided to retain SLA coverage:\n\n- **Storage full** : if your disk utilization is consistently high, and automatic storage increase is not enabled, your instance is not properly sized for your workload and may not be covered by the [SLA](/sql/sla).\n- **CPU overloaded** : if your CPU utilization is consistently high, your instance is not properly sized for your workload, and may not be covered by the [SLA](/sql/sla).\n- **Memory overloaded** : if your memory usage is consistently high, your instance is not properly sized for your workload, and may not be covered by the [SLA](/sql/sla).\n\nFor more information, refer to the [General best practices](/sql/docs/best-practices).\n\n\u003cbr /\u003e"]]
