How to configure Azure Cache for Redis
This article describes the configurations available for your Azure Cache for Redis instances. This article also covers the default Redis server configuration for Azure Cache for Redis instances.
Configure Azure Cache for Redis settings
To create a cache, sign in to the Azure portal and select Create a resource.
On the New page, select Databases and then select Azure Cache for Redis.
On the New Redis Cache page, configure the settings for your new cache.
Setting Choose a value Description Subscription Drop down and select your subscription. The subscription under which to create this new Azure Cache for Redis instance. Resource group Drop down and select a resource group, or select Create new and enter a new resource group name. Name for the resource group in which to create your cache and other resources. By putting all your app resources in one resource group, you can easily manage or delete them together. DNS name Enter a unique name. The cache name must be a string between 1 and 63 characters that contain only numbers, letters, or hyphens. The name must start and end with a number or letter, and can't contain consecutive hyphens. Your cache instance's host name will be <DNS name>.redis.cache.windows.net. Location Drop down and select a location. Select a region near other services that will use your cache. Cache type Drop down and select a tier. The tier determines the size, performance, and features that are available for the cache. For more information, see Azure Cache for Redis Overview.
Select the Networking tab or select the Networking button at the bottom of the page.
In the Networking tab, select your connectivity method.
Select the Next: Advanced tab or select the Next: Advanced button on the bottom of the page.
In the Advanced tab for a basic or standard cache instance, select the enable toggle if you want to enable a non-TLS port. You can also select which Redis version you would like use, either 4 or 6.
In the Advanced tab for premium cache instance, configure the settings for non-TLS port, clustering, and data persistence. You can also select which Redis version you would like use, either 4 or 6.
Select the Next: Tags tab or select the Next: Tags button at the bottom of the page.
Optionally, in the Tags tab, enter the name and value if you wish to categorize the resource.
Select Review + create. You're taken to the Review + create tab where Azure validates your configuration.
After the green Validation passed message appears, select Create.
It takes a while for the cache to create. You can monitor progress on the Azure Cache for Redis Overview page. When Status shows as Running, the cache is ready to use.
You can view and configure the following settings using the Resource Menu. The settings that you see depend on the tier of your cache. For example, you don't see Reboot when using the Enterprise tier.
- Activity log
- Access control (IAM)
- Diagnose and solve problems
- Support & troubleshooting settings
The Overview section provides you with basic information about your cache, such as name, ports, pricing tier, and selected cache metrics.
Select Activity log to view actions done to your cache. You can also use filtering to expand this view to include other resources. For more information on working with audit logs, see Audit operations with Resource Manager. For more information on monitoring Azure Cache for Redis events, see Create alerts.
Access control (IAM)
The Access control (IAM) section provides support for Azure role-based access control (Azure RBAC) in the Azure portal. This configuration helps organizations meet their access management requirements simply and precisely. For more information, see Azure role-based access control in the Azure portal.
The Tags section helps you organize your resources. For more information, see Using tags to organize your Azure resources.
Diagnose and solve problems
Select Diagnose and solve problems to be provided with common issues and strategies for resolving them.
Select Events to add event subscriptions to your cache. Use events to build reactive, event-driven apps with the fully managed event routing service that is built into Azure.
The Event Grid helps you build automation into your cloud infrastructure, create serverless apps, and integrate across services and clouds. For more information, see What is Azure Event Grid.
You can securely issue commands to your Azure Cache for Redis instances using the Redis Console, which is available in the Azure portal for all cache tiers.
The Redis Console does not work with VNet. When your cache is part of a VNet, only clients in the VNet can access the cache. Because Redis Console runs in your local browser, which is outside the VNet, it can't connect to your cache.
To access the Redis Console, select Console tab in the working pane of Resource menu.
To issue commands against your cache instance, type the command you want into the console.
Not all Redis commands are supported in Azure Cache for Redis. For a list of Redis commands that are disabled for Azure Cache for Redis, see Redis commands not supported in Azure Cache for Redis section. For more information about Redis commands, see https://redis.io/commands.
Using the Redis Console with a premium clustered cache
When using the Redis Console with a premium clustered cache, you can issue commands to a single shard of the cache. To issue a command to a specific shard, first connect to the shard you want by selecting it on the shard picker.
If you attempt to access a key that is stored in a different shard than the connected shard, you receive an error message similar to the following message:
shard1>get myKey (error) MOVED 866 126.96.36.199:13000 (shard 0) shard1>get myKey (error) MOVED 866 188.8.131.52:13000 (shard 0)
In the previous example, shard 1 is the selected shard, but
myKey is located in shard 0, as indicated by the
(shard 0) portion of the error message. In this example, to access
myKey, select shard 0 using the shard picker, and then issue the desired command.
Move your cache to a new subscription
You can move your cache to a new subscription by selecting Move.
For information on moving resources from one resource group to another, and from one subscription to another, see Move resources to new resource group or subscription.
The Settings section allows you to access and configure the following settings for your cache.
- Access keys
- Advanced settings
- Cluster size
- Data persistence
- Schedule updates
- Private endpoint
- Virtual Network
Select Access keys to view or regenerate the access keys for your cache. These keys are used by the clients connecting to your cache.
The following settings are configured on the Advanced settings on the left.
By default, non-TLS/SSL access is disabled for new caches. To enable the non-TLS port, Select No for Allow access only via SSL on the Advanced settings on the left and then Select Save.
TLS access to Azure Cache for Redis supports TLS 1.0, 1.1 and 1.2 currently, but versions 1.0 and 1.1 are being retired soon. Please read our Remove TLS 1.0 and 1.1 page for more details.
Use the Maxmemory policy, maxmemory-reserved, and maxfragmentationmemory-reserved settings from Advanced settings from the Resource menu on the left to configure the memory policies for the cache. When you create a cache, the values
maxfragmentationmemory-reserved default to 10% of
maxmemory, which is the cache size.
Maxmemory policy configures the eviction policy for the cache and allows you to choose from the following eviction policies:
volatile-lru: The default eviction policy, removes the least recently used key out of all the keys with an expiration set.
allkeys-lru: Removes the least recently used key.
volatile-random: Removes a random key that has an expiration set.
allkeys-random: Removes a random key.
volatile-ttl: Removes the key with the shortest time to live based on the expiration set for it.
noeviction: No eviction policy. Returns an error message if you attempt to insert data.
volatile-lfu: Evicts the least frequently used keys out of all keys with an expire field set.
allkeys-lfu: Evicts the least frequently used keys out of all keys.
For more information about
maxmemory policies, see Eviction policies.
The maxmemory-reserved setting configures the amount of memory in MB per instance in a cluster that is reserved for non-cache operations, such as replication during failover. Setting this value allows you to have a more consistent Redis server experience when your load varies. This value should be set higher for workloads that write large amounts of data. When memory is reserved for such operations, it's unavailable for storage of cached data. The minimum and maximum values on the slider are 10% and 60%, shown in megabytes. You must set the value in that range.
The maxfragmentationmemory-reserved setting configures the amount of memory in MB per instance in a cluster that is reserved to accommodate for memory fragmentation. When you set this value, the Redis server experience is more consistent when the cache is full or close to full and the fragmentation ratio is high. When memory is reserved for such operations, it's unavailable for storage of cached data. The minimum and maximum values on the slider are 10% and 60%, shown in megabytes. You must set the value in that range.
When choosing a new memory reservation value (maxmemory-reserved or maxfragmentationmemory-reserved), consider how this change might affect a cache that is already running with large amounts of data in it. For instance, if you have a 53-GB cache with 49 GB of data, then change the reservation value to 8 GB, this change drops the max available memory for the system down to 45 GB. If either your current
used_memory or your
used_memory_rss values are higher than the new limit of 45 GB, then the system will have to evict data until both
used_memory_rss are below 45 GB. Eviction can increase server load and memory fragmentation. For more information on cache metrics such as
used_memory_rss, see Create your own metrics.
The maxmemory-reserved and maxfragmentationmemory-reserved settings are available only for Standard and Premium caches.
Keyspace notifications (advanced settings)
Redis keyspace notifications are configured on the Advanced settings on the left. Keyspace notifications allow clients to receive notifications when certain events occur.
Keyspace notifications and the notify-keyspace-events setting are only available for Standard and Premium caches.
Select Scale to view or change the pricing tier for your cache. For more information on scaling, see How to Scale Azure Cache for Redis.
Select Cluster Size to change the cluster size for a running premium cache with clustering enabled.
To change the cluster size, use the slider or type a number between 1 and 10 in the Shard count text box. Then, select OK to save.
Redis clustering is only available for Premium caches. For more information, see How to configure clustering for a Premium Azure Cache for Redis.
Select Data persistence to enable, disable, or configure data persistence for your premium cache. Azure Cache for Redis offers Redis persistence using either RDB persistence or AOF persistence.
For more information, see How to configure persistence for a Premium Azure Cache for Redis.
Redis data persistence is only available for Premium caches.
Use Identity to configure managed identities. Managed identities are a common tool used in Azure to help developers minimize the burden of managing secrets and sign-in information.
Presently, you can only use managed identities for storage. For more information, see Managed identity for storage.
Managed identity functionality is only available in the Premium tier for use with storage.
The Schedule updates section on the left allows you to choose a maintenance window for Redis server updates for your cache.
The maintenance window applies only to Redis server updates, and not to any Azure updates or updates to the operating system of the VMs that host the cache.
To specify a maintenance window, check the days you want. Then, specify the maintenance window start hour for each day, and select OK. The maintenance window time is in UTC.
For more information and instructions, see Azure Cache for Redis administration - Schedule updates
Geo-replication, on the left, provides a mechanism for linking two Premium tier Azure Cache for Redis instances. One cache is named as the primary linked cache, and the other as the secondary linked cache. The secondary linked cache becomes read-only, and data written to the primary cache is replicated to the secondary linked cache. This functionality can be used to replicate a cache across Azure regions.
Geo-replication is only available for Premium tier caches. For more information and instructions, see How to configure Geo-replication for Azure Cache for Redis.
The Virtual Network section allows you to configure the virtual network settings for your cache. Virtual networks are limited to Premium caches. For information on creating a premium cache with VNET support and updating its settings, see How to configure Virtual Network Support for a Premium Azure Cache for Redis.
Virtual network settings are only available for premium caches that were configured with VNet support during cache creation.
The Private Endpoint section allows you to configure the private endpoint settings for your cache. Private endpoint is supported on all cache tiers Basic, Standard, Premium, and Enterprise. We recommend using private endpoint instead of VNets. Private endpoints are easy to set up or remove, are supported on all tiers, and can connect your cache to multiple different VNets at once.
For more information, see Azure Cache for Redis with Azure Private Link.
- Firewall rules configuration is available for all Basic, Standard, and Premium tiers.
- Firewall rules configuration isn't available for Enterprise nor Enterprise Flash tiers.
Select Firewall to view and configure firewall rules for cache.
You can specify firewall rules with a start and end IP address range. When firewall rules are configured, only client connections from the specified IP address ranges can connect to the cache. When a firewall rule is saved, there's a short delay before the rule is effective. This delay is typically less than one minute.
Connections from Azure Cache for Redis monitoring systems are always permitted, even if firewall rules are configured.
Select Properties to view information about your cache, including the cache endpoint and ports.
The Locks section allows you to lock a subscription, resource group, or resource to prevent other users in your organization from accidentally deleting or modifying critical resources. For more information, see Lock resources with Azure Resource Manager.
The settings in the Administration section allow you to perform the following administrative tasks for your cache.
Import/Export is an Azure Cache for Redis data management operation that allows you to import and export data in the cache. You can import and export an Azure Cache for Redis Database (RDB) snapshot from a premium cache to a page blob in an Azure Storage Account. Use Import/Export to migrate between different Azure Cache for Redis instances or populate the cache with data before use.
You can use import with Redis-compatible RDB files from any Redis server running in any cloud or environment:
- including Redis running on Linux
- any cloud provider such as Amazon Web Services and others
Importing data is an easy way to create a cache with pre-populated data. During the import process, Azure Cache for Redis loads the RDB files from Azure storage into memory, and then inserts the keys into the cache.
Export allows you to export the data stored in Azure Cache for Redis to Redis compatible RDB files. You can use this feature to move data from one Azure Cache for Redis instance to another or to another Redis server. During the export process, a temporary file is created on the VM that hosts the Azure Cache for Redis server instance. The temporary file is uploaded to the designated storage account. When the export operation completes with either a status of success or failure, the temporary file is deleted.
Import/Export is only available for Premium tier caches. For more information and instructions, see Import and Export data in Azure Cache for Redis.
The Reboot item on the left allows you to reboot the nodes of your cache. This reboot capability enables you to test your application for resiliency if there's a failure of a cache node.
If you have a premium cache with clustering enabled, you can select which shards of the cache to reboot.
To reboot one or more nodes of your cache, select the desired nodes and select Reboot. If you have a premium cache with clustering enabled, select the shards to reboot, and then select Reboot. After a few minutes, the selected node(s) reboot, and are back online a few minutes later.
Reboot is not yet available for the Enterprise tier. Reboot is available for all other tiers. For more information and instructions, see Azure Cache for Redis administration - Reboot.
The Monitoring section allows you to configure diagnostics and monitoring for your Azure Cache for Redis. For more information on Azure Cache for Redis monitoring and diagnostics, see How to monitor Azure Cache for Redis.
Use Insights to see groups of predefined tiles and charts to use as starting point for your cache metrics.
For more information, see Use Insights for predefined charts.
Select Metrics to Create your own custom chart to track the metrics you want to see for your cache. For more information, see Create alerts.
Select Alerts to configure alerts based on Azure Cache for Redis metrics. For more information, see Create alerts.
By default, cache metrics in Azure Monitor are stored for 30 days and then deleted. To persist your cache metrics for longer than 30 days, select Diagnostics settings to configure the storage account used to store cache diagnostics.
In addition to archiving your cache metrics to storage, you can also stream them to an Event hub or send them to Azure Monitor logs.
The Advisor recommendations on the left displays recommendations for your cache. During normal operations, no recommendations are displayed.
If any conditions occur during the operations of your cache such as imminent changes, high memory usage, network bandwidth, or server load, an alert is displayed in the Overview of the Resource menu.
Further information can be found on the Recommendations in the working pane of the Azure portal.
You can monitor these metrics on the Monitoring section of the Resource menu.
Each pricing tier has different limits for client connections, memory, and bandwidth. If your cache approaches maximum capacity for these metrics over a sustained period of time, a recommendation is created. For more information about the metrics and limits reviewed by the Recommendations tool, see the following table:
|Azure Cache for Redis metric||More information|
|Network bandwidth usage||Cache performance - available bandwidth|
|Connected clients||Default Redis server configuration - max clients|
|Server load||Redis Server Load|
|Memory usage||Cache performance - size|
Organize your metrics into groups so that you display metric information in a coherent and effective way.
Azure Automation delivers a cloud-based automation, operating system updates, and configuration service that supports consistent management across your Azure and non-Azure environments.
Select Tasks to help you manage Azure Cache for Redis resources more easily. These tasks vary in number and availability, based on the resource type. Presently, you can only use the Send monthly cost for resource template to create a task while in preview.
For more information, see Manage Azure resources and monitor costs by creating automation tasks.
Select Export template to build and export a template of your deployed resources for future deployments. For more information about working with templates, see Deploy resources with Azure Resource Manager templates.
Support & troubleshooting settings
The settings in the Support + troubleshooting section provide you with options for resolving issues with your cache.
Resource health watches your resource and tells you if it's running as expected. For more information about the Azure Resource health service, see Azure Resource health overview.
Resource health is currently unable to report on the health of Azure Cache for Redis instances hosted in a virtual network. For more information, see Do all cache features work when hosting a cache in a VNET?
New support request
Select New support request to open a support request for your cache.
Default Redis server configuration
New Azure Cache for Redis instances are configured with the following default Redis configuration values:
The settings in this section cannot be changed using the
StackExchange.Redis.IServer.ConfigSet method. If this method is called with one of the commands in this section, an exception similar to the following example is thrown:
StackExchange.Redis.RedisServerException: ERR unknown command 'CONFIG'
Any values that are configurable, such as max-memory-policy, are configurable through the Azure portal or command-line management tools such as Azure CLI or PowerShell.
||16||The default number of databases is 16 but you can configure a different number based on the pricing tier.1 The default database is DB 0, you can select a different one on a per-connection basis using
||Depends on the pricing tier2||This value is the maximum number of connected clients allowed at the same time. Once the limit is reached Redis closes all the new connections, returning a 'max number of clients reached' error.|
||The allowed range for
||The allowed range for
||Maxmemory policy is the setting used by the Redis server to select what to remove when
||3||To save memory, LRU and minimal TTL algorithms are approximated algorithms instead of precise algorithms. By default Redis checks three keys and picks the one that was used less recently.|
||5,000||Max execution time of a Lua script in milliseconds. If the maximum execution time is reached, Redis logs that a script is still in execution after the maximum allowed time, and starts to reply to queries with an error.|
||500||Max size of script event queue.|
||0 0 032mb 8 mb 60||The client output buffer limits can be used to force disconnection of clients that aren't reading data from the server fast enough for some reason. A common reason is that a Pub/Sub client can't consume messages as fast as the publisher can produce them. For more information, see https://redis.io/topics/clients.|
1The limit for
databases is different for each Azure Cache for Redis pricing tier and can be set at cache creation. If no
databases setting is specified during cache creation, the default is 16.
- Basic and Standard caches
- C0 (250 MB) cache - up to 16 databases
- C1 (1 GB) cache - up to 16 databases
- C2 (2.5 GB) cache - up to 16 databases
- C3 (6 GB) cache - up to 16 databases
- C4 (13 GB) cache - up to 32 databases
- C5 (26 GB) cache - up to 48 databases
- C6 (53 GB) cache - up to 64 databases
- Premium caches
- P1 (6 GB - 60 GB) - up to 16 databases
- P2 (13 GB - 130 GB) - up to 32 databases
- P3 (26 GB - 260 GB) - up to 48 databases
- P4 (53 GB - 530 GB) - up to 64 databases
- P5 (120 GB - 1200 GB) - up to 64 databases
- All premium caches with Redis cluster enabled - Redis cluster only supports use of database 0 so the
databaseslimit for any premium cache with Redis cluster enabled is effectively 1 and the Select command isn't allowed. For more information, see Do I need to make any changes to my client application to use clustering?
For more information about databases, see What are Redis databases?
databases setting can be configured only during cache creation and only using PowerShell, CLI, or other management clients. For an example of configuring
databases during cache creation using PowerShell, see New-AzRedisCache.
maxclients is different for each Azure Cache for Redis pricing tier.
- Basic and Standard caches
- C0 (250 MB) cache - up to 256 connections
- C1 (1 GB) cache - up to 1,000 connections
- C2 (2.5 GB) cache - up to 2,000 connections
- C3 (6 GB) cache - up to 5,000 connections
- C4 (13 GB) cache - up to 10,000 connections
- C5 (26 GB) cache - up to 15,000 connections
- C6 (53 GB) cache - up to 20,000 connections
- Premium caches
- P1 (6 GB - 60 GB) - up to 7,500 connections
- P2 (13 GB - 130 GB) - up to 15,000 connections
- P3 (26 GB - 260 GB) - up to 30,000 connections
- P4 (53 GB - 530 GB) - up to 40,000 connections
- P5: (120 GB - 1200 GB) - up to 40,000 connections
While each size of cache allows up to a certain number of connections, each connection to Redis has overhead associated with it. An example of such overhead would be CPU and memory usage as a result of TLS/SSL encryption. The maximum connection limit for a given cache size assumes a lightly loaded cache. If load from connection overhead plus load from client operations exceeds capacity for the system, the cache can experience capacity issues even if you have not exceeded the connection limit for the current cache size.
Redis commands not supported in Azure Cache for Redis
Configuration and management of Azure Cache for Redis instances is managed by Microsoft, which disables the following commands. If you try to invoke them, you receive an error message similar to
"(error) ERR unknown command".
- CLUSTER - Cluster write commands are disabled, but read-only Cluster commands are permitted.
For cache instances using active geo-replication, the following commands are also blocked to prevent accidental data loss:
Because configuration and management of Azure Cache for Redis instances is managed by Microsoft, some commands are disabled. The commands are listed above. If you try to invoke them, you receive an error message similar to
"(error) ERR unknown command".
For more information about Redis commands, see https://redis.io/commands.