You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
15
16
16
17
> [!NOTE]
@@ -19,6 +20,7 @@ This article describes the configurations available for your Azure Cache for Red
Azure Cache for Redis settings are viewed and configured on the **Azure Cache for Redis** on the left using the **Resource Menu**.
@@ -33,32 +35,31 @@ You can view and configure the following settings using the **Resource Menu**.
33
35
*[Tags](#tags)
34
36
*[Diagnose and solve problems](#diagnose-and-solve-problems)
35
37
*[Settings](#settings)
36
-
* [Access keys](#access-keys)
37
-
* [Advanced settings](#advanced-settings)
38
-
* [Azure Cache for Redis Advisor](#azure-cache-for-redis-advisor)
39
-
* [Scale](#scale)
40
-
* [Cluster size](#cluster-size)
41
-
* [Data persistence](#redis-data-persistence)
42
-
* [Schedule updates](#schedule-updates)
43
-
* [Geo-replication](#geo-replication)
44
-
* [Virtual Network](#virtual-network)
45
-
* [Firewall](#firewall)
46
-
* [Properties](#properties)
47
-
* [Locks](#locks)
48
-
* [Automation script](#automation-script)
38
+
*[Access keys](#access-keys)
39
+
*[Advanced settings](#advanced-settings)
40
+
*[Azure Cache for Redis Advisor](#azure-cache-for-redis-advisor)
41
+
*[Scale](#scale)
42
+
*[Cluster size](#cluster-size)
43
+
*[Data persistence](#redis-data-persistence)
44
+
*[Schedule updates](#schedule-updates)
45
+
*[Geo-replication](#geo-replication)
46
+
*[Virtual Network](#virtual-network)
47
+
*[Firewall](#firewall)
48
+
*[Properties](#properties)
49
+
*[Locks](#locks)
50
+
*[Automation script](#automation-script)
49
51
* Administration
50
-
* [Import data](#importexport)
51
-
* [Export data](#importexport)
52
-
* [Reboot](#reboot)
52
+
*[Import data](#importexport)
53
+
*[Export data](#importexport)
54
+
*[Reboot](#reboot)
53
55
*[Monitoring](#monitoring)
54
-
* [Redis metrics](#redis-metrics)
55
-
* [Alert rules](#alert-rules)
56
-
[Diagnostics](#diagnostics)
56
+
*[Redis metrics](#redis-metrics)
57
+
*[Alert rules](#alert-rules)
58
+
*[Diagnostics](#diagnostics)
57
59
* Support & troubleshooting settings
58
60
*[Resource health](#resource-health)
59
61
*[New support request](#new-support-request)
60
62
61
-
62
63
## Overview
63
64
64
65
**Overview** provides you with basic information about your cache, such as name, ports, pricing tier, and selected cache metrics.
@@ -75,14 +76,12 @@ The **Access control (IAM)** section provides support for Azure role-based acces
75
76
76
77
The **Tags** section helps you organize your resources. For more information, see [Using tags to organize your Azure resources](../azure-resource-manager/management/tag-resources.md).
77
78
78
-
79
79
### Diagnose and solve problems
80
80
81
81
Select **Diagnose and solve problems** to be provided with common issues and strategies for resolving them.
82
82
83
-
84
-
85
83
## Settings
84
+
86
85
The **Settings** section allows you to access and configure the following settings for your cache.
87
86
88
87
*[Access keys](#access-keys)
@@ -99,21 +98,22 @@ The **Settings** section allows you to access and configure the following settin
99
98
*[Locks](#locks)
100
99
*[Automation script](#automation-script)
101
100
102
-
103
-
104
101
### Access keys
102
+
105
103
Select **Access keys** to view or regenerate the access keys for your cache. These keys are used by the clients connecting to your cache.
106
104
107
105

108
106
109
107
### Advanced settings
108
+
110
109
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**.
118
118
119
119
> [!NOTE]
@@ -122,7 +122,9 @@ By default, non-TLS/SSL access is disabled for new caches. To enable the non-TLS
122
122

The **Maxmemory policy**, **maxmemory-reserved**, and **maxfragmentationmemory-reserved** settings on the **Advanced settings** on the left configure the memory policies for the cache.
127
129
128
130

@@ -140,17 +142,18 @@ For more information about `maxmemory` policies, see [Eviction policies](https:/
140
142
141
143
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.
142
144
143
-
The **maxfragmentationmemory-reserved** setting configures the amount of memory, in MB per instance in a cluster, that is reserved to accommodate for memory fragmentation. Setting this value allows you to have a more consistent Redis server experience 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.
145
+
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, you to have a more consistent Redis server experience 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.
144
146
145
147
One thing to consider when choosing a new memory reservation value (**maxmemory-reserved** or **maxfragmentationmemory-reserved**) is 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 will drop 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` and `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` and `used_memory_rss`, see [Available metrics and reporting intervals](cache-how-to-monitor.md#available-metrics-and-reporting-intervals).
146
148
147
149
> [!IMPORTANT]
148
150
> The **maxmemory-reserved** and **maxfragmentationmemory-reserved** settings are available only for Standard and Premium caches.
149
-
>
151
+
>
150
152
> The `noeviction` eviction policy is the only memory policy that's available for an Enterprise tier cache.
151
153
>
152
154
153
155
#### Keyspace notifications (advanced settings)
156
+
154
157
Redis keyspace notifications are configured on the **Advanced settings** on the left. Keyspace notifications allow clients to receive notifications when certain events occur.
155
158
156
159

@@ -162,9 +165,10 @@ Redis keyspace notifications are configured on the **Advanced settings** on the
162
165
163
166
For more information, see [Redis Keyspace Notifications](https://redis.io/topics/notifications). For sample code, see the [KeySpaceNotifications.cs](https://github.com/rustd/RedisSamples/blob/master/HelloWorld/KeySpaceNotifications.cs) file in the [Hello world](https://github.com/rustd/RedisSamples/tree/master/HelloWorld) sample.
164
167
165
-
166
168
<aname="recommendations"></a>
169
+
167
170
## Azure Cache for Redis Advisor
171
+
168
172
The **Azure Cache for Redis Advisor** on the left displays recommendations for your cache. During normal operations, no recommendations are displayed.
169
173
170
174

@@ -211,20 +215,19 @@ To change the cluster size, use the slider or type a number between 1 and 10 in
211
215
>
212
216
>
213
217
214
-
215
218
### Redis data persistence
216
219
217
220
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.
218
221
219
222
For more information, see [How to configure persistence for a Premium Azure Cache for Redis](cache-how-to-premium-persistence.md).
220
223
221
-
222
224
> [!IMPORTANT]
223
225
> Redis data persistence is only available for Premium caches.
224
226
>
225
227
>
226
228
227
229
### Schedule updates
230
+
228
231
The **Schedule updates on the left allow you to choose a maintenance window for Redis server updates for your cache.
229
232
230
233
> [!IMPORTANT]
@@ -248,6 +251,7 @@ For more information and instructions, see [Azure Cache for Redis administration
248
251
>
249
252
250
253
### Virtual Network
254
+
251
255
The **Virtual Network** section allows you to configure the virtual network settings for your cache. 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](cache-how-to-premium-vnet.md).
252
256
253
257
> [!IMPORTANT]
@@ -271,18 +275,21 @@ You can specify firewall rules with a start and end IP address range. When firew
271
275
>
272
276
273
277
### Properties
278
+
274
279
Select **Properties** to view information about your cache, including the cache endpoint and ports.
275
280
276
281

277
282
278
283
### Locks
284
+
279
285
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](../azure-resource-manager/management/lock-resources.md).
280
286
281
287
### Automation script
282
288
283
289
Select **Automation script** 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](../azure-resource-manager/templates/deploy-powershell.md).
284
290
285
291
## Administration settings
292
+
286
293
The settings in the **Administration** section allow you to perform the following administrative tasks for your cache.
@@ -291,8 +298,8 @@ The settings in the **Administration** section allow you to perform the followin
291
298
*[Export data](#importexport)
292
299
*[Reboot](#reboot)
293
300
294
-
295
301
### Import/Export
302
+
296
303
Import/Export is an Azure Cache for Redis data management operation, which allows you to import and export data in the cache by importing and exporting an Azure Cache for Redis Database (RDB) snapshot from a premium cache to a page blob in an Azure Storage Account. Import/Export enables you to migrate between different Azure Cache for Redis instances or populate the cache with data before use.
297
304
298
305
Import can be used to bring Redis compatible RDB files from any Redis server running in any cloud or environment, including Redis running on Linux, Windows, or 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.
@@ -305,6 +312,7 @@ Export allows you to export the data stored in Azure Cache for Redis to Redis co
305
312
>
306
313
307
314
### Reboot
315
+
308
316
The **Reboot** 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 is a failure of a cache node.
@@ -357,6 +366,7 @@ The settings in the **Support + troubleshooting** section provide you with optio
357
366
*[New support request](#new-support-request)
358
367
359
368
### Resource health
369
+
360
370
**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](../service-health/resource-health-overview.md).
361
371
362
372
> [!NOTE]
@@ -365,13 +375,11 @@ The settings in the **Support + troubleshooting** section provide you with optio
365
375
>
366
376
367
377
### New support request
368
-
Select **New support request** to open a support request for your cache.
369
-
370
-
371
-
372
378
379
+
Select **New support request** to open a support request for your cache.
373
380
374
381
## Default Redis server configuration
382
+
375
383
New Azure Cache for Redis instances are configured with the following default Redis configuration values:
376
384
377
385
> [!NOTE]
@@ -440,9 +448,8 @@ For more information about databases, see [What are Redis databases?](cache-deve
440
448
>
441
449
>
442
450
443
-
444
-
445
451
## Redis commands not supported in Azure Cache for Redis
452
+
446
453
> [!IMPORTANT]
447
454
> Because configuration and management of Azure Cache for Redis instances is managed by Microsoft, the following commands are disabled. If you try to invoke them, you receive an error message similar to `"(error) ERR unknown command"`.
448
455
>
@@ -461,11 +468,13 @@ For more information about databases, see [What are Redis databases?](cache-deve
461
468
For more information about Redis commands, see [https://redis.io/commands](https://redis.io/commands).
462
469
463
470
## Redis console
471
+
464
472
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.
465
473
466
474
> [!IMPORTANT]
467
-
> - The Redis Console does not work with [VNET](cache-how-to-premium-vnet.md). 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.
468
-
> - 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 the previous [Redis commands not supported in Azure Cache for Redis](#redis-commands-not-supported-in-azure-cache-for-redis) section. For more information about Redis commands, see [https://redis.io/commands](https://redis.io/commands).
475
+
>
476
+
> * The Redis Console does not work with [VNET](cache-how-to-premium-vnet.md). 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.
477
+
> * 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 the previous [Redis commands not supported in Azure Cache for Redis](#redis-commands-not-supported-in-azure-cache-for-redis) section. For more information about Redis commands, see [https://redis.io/commands](https://redis.io/commands).
469
478
>
470
479
>
471
480
@@ -477,7 +486,6 @@ To issue commands against your cache instance, type the command you want into th
477
486
478
487

479
488
480
-
481
489
### Using the Redis Console with a premium clustered cache
482
490
483
491
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.
@@ -493,13 +501,14 @@ shard1>get myKey
493
501
494
502
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.
495
503
496
-
497
504
## Move your cache to a new subscription
505
+
498
506
You can move your cache to a new subscription by selecting **Move**.
499
507
500
508

501
509
502
510
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](../azure-resource-manager/management/move-resource-group-and-subscription.md).
503
511
504
512
## Next steps
513
+
505
514
* For more information on working with Redis commands, see [How can I run Redis commands?](cache-development-faq.md#how-can-i-run-redis-commands)
0 commit comments