This page describes product constraints that you should take into consideration when planning and implementing your Memorystore for Redis solution.
Blocked Redis commands
Replication buffer for Standard Tier instances
Standard Tier Memorystore for Redis instances reserve 10% of primary-node memory for replication buffer usage. When monitoring your instance, this buffer appears in the used memory metric, even if the instance is empty.
Memorystore for Redis does not currently support maintenance windows. See the Memorystore for Redis Maintenance Policy for more details.
Basic Tier limitations
The Basic Tier is best used as a simple cache. Basic Tier Memorystore for Redis instances are subject to a cold-restart and full data flush in the following scenarios: routine maintenance, scaling, or an instance failure. Accordingly, you should only use Basic Tier instances when your application can withstand cold-restarts.
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.
Transport layer security support
Memorystore for Redis does not currently support Transport Layer Security (TLS).
You can connect only to a Memorystore for Redis instance from Google Cloud resources in the same region as your instance or from on-premises networks.