[[["容易理解","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 (世界標準時間)。"],[],[],null,["# Operational guidelines\n\nThe Memorystore for Redis Cluster [Service Level Agreement (SLA)](/memorystore/sla) excludes outages \"caused by factors outside of Google's reasonable control\". This page describes some of the user-controlled configurations and workloads that can cause an outage for a Memorystore for Redis Cluster instance to be excluded.\n\nIntroduction\n------------\n\nMemorystore strives to give you as much control over how your instance is configured and used as possible. This includes some configurations or workload patterns that increase the risk of instance downtime. If your instance becomes unhealthy and Memorystore determines that it was out of compliance with the operational limits and best practices as described on this page, then the downtime period is not covered by (or does not count against) the Memorystore [SLA](/memorystore/sla).\n\nThis list of operational limits and best practices is presented to inform you which configurations and workload patterns present these risks, ways to avoid them, and ways to mitigate the risks when the configuration is required for your business environment.\n\nExcluded configurations\n-----------------------\n\nThis section lists configurations that can cause your instance to be excluded from the Memorystore SLA.\n\n### General configuration requirements\n\n- If you configure a Memorystore for Redis Cluster instance without [high availability](/memorystore/docs/cluster/ha-and-replicas) (0 replicas), then the SLA doesn't apply. The Memorystore SLA covers only instances that are configured for high availability.\n- If you [disable or destroy the primary key version](/memorystore/docs/cluster/about-cmek#disable-or-destroy-a-cmek-key-version) for an instance, then the instance is excluded from the Memorystore SLA.\n\n### Resource constraints\n\nThe following resource constraints must be avoided to retain SLA coverage:\n\n- **CPU overloaded:** If your CPU utilization is consistently high, your instance is not properly sized for your workload or you are using Redis commands improperly. If CPU resources are overloaded, you may not be covered by the [SLA](/memorystore/sla).\n\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](/memorystore/sla).\n\n### `redis-shared-core-nano` node type\n\nThe Memorystore SLA doesn't apply to clusters that use the `redis-shared-core-nano` [node type](/memorystore/docs/cluster/cluster-node-specification). The node type isn't suitable for most production workloads because it has insufficient performance and is too small for most production use cases.\n\nBest practices\n--------------\n\n[Best practices for Memorystore for Redis Cluster](/memorystore/docs/cluster/general-best-practices) are published to ensure that you receive the best possible experience with Memorystore. Downtime events which result from you not following the published best practices may not be covered by the [SLA](/memorystore/sla)."]]
