Stay organized with collections
Save and categorize content based on your preferences.
This page describes product constraints that you should take into consideration
when planning and implementing your Memorystore for Redis solution.
Blocked Redis commands
ACL CAT
ACL DELUSER
ACL GENPASS
ACL GETUSER
ACL HELP
ACL LIST
ACL LOAD
ACL LOG
ACL SAVE
ACL SETUSER
ACL USERS
ACL WHOAMI
BGREWRITEAOF
BGSAVE
CLIENT
CLUSTER
COMMAND
CONFIG1
DEBUG
LASTSAVE
MIGRATE
MONITOR
OBJECT
SHUTDOWN
REPLICAOF
SAVE
1 Memorystore for Redis blocks the CONFIG command, which stops you
from modifying the redis.conf file for your Redis server. However, you can
use the gcloud CLI to modify a defined set of Supported Redis configurations.
Replication backlog for Standard Tier instances
Standard Tier Memorystore for Redis instances reserve 10% of primary-node
memory for replication backlog usage. When monitoring your instance,
this backlog appears in the used memory metric, even if the instance is
empty.
You can only run one admin operation at a time
Examples of Memorystore for Redis admin operations are resizing, renaming, and
changing other Redis instance configurations. Only one of these commands can be
run at a time. You will have to wait for any admin operation to complete before
you can run another one. During these operations, you can still run Redis
commands and access the data in the Redis instance.
Quotas and limits
For information on the Memorystore for Redis instance capacity quota and API
requests quota, see Quotas and Limits.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[],[],null,["# Product constraints\n\nThis page describes product constraints that you should take into consideration\nwhen planning and implementing your Memorystore for Redis solution.\n\nBlocked Redis commands\n----------------------\n\n| **Note:** The COMMAND, MONITOR, and OBJECT commands are available for instances created after November 4, 2019.\n\n- ACL CAT\n- ACL DELUSER\n- ACL GENPASS\n- ACL GETUSER\n- ACL HELP\n- ACL LIST\n- ACL LOAD\n- ACL LOG\n- ACL SAVE\n- ACL SETUSER\n- ACL USERS\n- ACL WHOAMI\n- BGREWRITEAOF\n- BGSAVE\n- CLIENT\n- CLUSTER\n- COMMAND\n- CONFIG^1^\n- DEBUG\n- LASTSAVE\n- MIGRATE\n- MONITOR\n- OBJECT\n- SHUTDOWN\n- REPLICAOF\n- SAVE\n\n^1^ Memorystore for Redis blocks the `CONFIG` command, which stops you\nfrom modifying the `redis.conf` file for your Redis server. However, you can\nuse the gcloud CLI to modify a defined set of [Supported Redis configurations](/memorystore/docs/redis/supported-redis-configurations).\n\nReplication backlog for Standard Tier instances\n-----------------------------------------------\n\nStandard Tier Memorystore for Redis instances reserve 10% of primary-node\nmemory for replication backlog usage. When [monitoring your instance](/memorystore/docs/redis/monitoring-instances),\nthis backlog appears in the **used memory** metric, even if the instance is\nempty.\n\nYou can only run one admin operation at a time\n----------------------------------------------\n\nExamples of Memorystore for Redis admin operations are resizing, renaming, and\nchanging other Redis instance configurations. Only one of these commands can be\nrun at a time. You will have to wait for any admin operation to complete before\nyou can run another one. During these operations, you can still run Redis\ncommands and access the data in the Redis instance.\n\nQuotas and limits\n-----------------\n\nFor information on the Memorystore for Redis instance capacity quota and API\nrequests quota, see [Quotas and Limits](/memorystore/docs/redis/quotas)."]]
