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
Copy file name to clipboardExpand all lines: articles/redis/configure.md
+4-101Lines changed: 4 additions & 101 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,8 +13,7 @@ appliesto:
13
13
14
14
# How to configure Azure Managed Redis
15
15
16
-
This article describes the configurations available for your Azure Managed Redis instances. This article also covers the [default Redis server configuration](#default-redis-server-configuration) for Azure Managed Redis instances.
17
-
16
+
This article describes the configurations available for your Azure Managed Redis instances.
18
17
19
18
## Configure Azure Managed Redis settings
20
19
@@ -25,19 +24,13 @@ You can view and configure the following settings using the **Resource Menu**.
25
24
-[Access control (IAM)](#access-control-iam)
26
25
-[Tags](#tags)
27
26
-[Diagnose and solve problems](#diagnose-and-solve-problems)
28
-
<!-- - Redis console -->
29
-
<!-- - [Move to a new subscription](#move-your-cache-to-a-new-subscription) -->
@@ -77,18 +70,6 @@ The **Tags** section helps you organize your resources. For more information, se
77
70
78
71
Select **Diagnose and solve problems** to be provided with common issues and strategies for resolving them.
79
72
80
-
<!-- ## Redis console
81
-
82
-
Direct access to the Redis console is not yet supported in Azure Managed Redis. Instead, consider using the [Redis CLI](how-to-redis-cli-tool.md) or a tool like [Redis Insight](https://redis.io/insight/). -->
83
-
84
-
<!-- ## Move your cache to a new subscription
85
-
86
-
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](/azure/azure-resource-manager/management/move-resource-group-and-subscription). -->
91
-
92
73
## Settings
93
74
94
75
The **Settings** section allows you to access and configure the following settings for your cache.
@@ -123,45 +104,6 @@ Select **Microsoft Entra Authentication** to a password-free authentication mec
123
104
124
105
The following settings are configured on the **Advanced settings** on the left.
<!-- The only settings I see are Non-TLS access, Eviction Policy, Defer Redis DB Version -->
132
-
<!--
133
-
#### Access Ports
134
-
135
-
By default, only TLS access is enabled for new caches. To enable non-TLS access, Select **Enable** for **Non-TLS access only** and then Select **Save**.
136
-
137
-
> [!NOTE]
138
-
> Azure Managed Redis supports TLS 1.2 and 1.3. See [What are the configuration settings for the TLS protocol?](tls-configuration.md) for more details.
139
-
> -->
140
-
141
-
<!-- #### Memory policies
142
-
143
-
When you create a cache, approximately 20% of the instance memory is reserved as a memory buffer for replication and other system processes. This helps the instance operate more effectively. -->
144
-
145
-
<!-- **Eviction policy** configures the eviction policy for the cache and allows you to choose from the following eviction policies:
146
-
147
-
- `volatile-lru`: The default eviction policy. It removes the least recently used key out of all the keys with an expiration set.
148
-
- `allkeys-lru`: Removes the least recently used key.
149
-
- `volatile-random`: Removes a random key that has an expiration set.
150
-
- `allkeys-random`: Removes a random key.
151
-
- `volatile-ttl`: Removes the key with the shortest time to live based on the expiration set for it.
152
-
- `noeviction`: No eviction policy. Returns an error message if you attempt to insert data.
153
-
- `volatile-lfu`: Evicts the least frequently used keys out of all keys with an expire field set.
154
-
- `allkeys-lfu`: Evicts the least frequently used keys out of all keys.
155
-
156
-
For more information, see [Eviction policies](https://redis.io/topics/lru-cache#eviction-policies). -->
157
-
158
-
<!-- #### Keyspace notifications
159
-
160
-
Redis keyspace notifications are configured using the **notify-keyspace-events** box. Keyspace notifications allow clients to receive notifications when certain events occur.
161
-
Keyspace notifications can be used to [trigger Azure Functions](tutorial-functions-getting-started.md) based on activity on your Redis instance.
162
-
163
-
For more information, see [Redis Keyspace Notifications](https://redis.io/topics/notifications).-->
164
-
165
107
### Data persistence (preview)
166
108
167
109
**Data persistence** allows you to enable, disable, or configure data persistence for your Redis instance. Azure Managed Redis offers Redis persistence using either RDB persistence or AOF persistence.
@@ -182,26 +124,6 @@ For more information, see [Configure active geo-replication for Azure Managed Re
182
124
183
125
Select **Scale** to view or change the size and performance tier of your Redis instance. For more information on scaling, see [How to Scale Azure Managed Redis](how-to-scale.md).
184
126
185
-
<!-- ### Schedule updates
186
-
187
-
Scheduled updates are not yet available in Azure Managed Redis. -->
188
-
189
-
<!--
190
-
The **Schedule updates** section allows you to choose a maintenance window for Redis server updates for your cache.
191
-
192
-
193
-
> [!IMPORTANT]
194
-
> 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.
199
-
200
-
For more information and instructions, see [Update channel and Schedule updates](administration.md#update-channel-and-schedule-updates).
201
-
-->
202
-
203
-
<!-- ### Identity this missing from the list/toc -->
204
-
205
127
### Properties
206
128
207
129
Select **Properties** to view information about your instance, including the endpoint, Redis DB version, and clustering policy.
@@ -262,7 +184,7 @@ Select **Metrics** to create your own custom chart to track the metrics you want
262
184
263
185
The **Advisor recommendations** displays recommendations for your cache. During normal operations, no recommendations are displayed.
264
186
265
-
<!--I'm keeping the screenshots in this section because they're kind of necessary. But they should be updated at some point -->
187
+
<!--The screenshots in this section should be updated at some point -->
266
188
267
189
:::image type="content" source="media/configure/redis-cache-no-recommendations.png" alt-text="Screenshot that shows where the Advisor recommendations are displayed but there are no current ones.":::
268
190
@@ -321,25 +243,6 @@ Select **Support + Troubleshooting** to open a support request for your cache.
321
243
322
244
## Other configuration information
323
245
324
-
### Default Redis server configuration
325
-
326
-
New Azure Managed Redis instances are configured with the following default Redis configuration values:
327
-
328
-
| Setting | Default value | Description |
329
-
| --- | --- | --- |
330
-
|`maxclients`|Depends on the pricing tier<sup>2</sup> |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. |
331
-
|`maxmemory-reserved`| 20% of `maxmemory`| 20% of memory is reserved for replication buffers and other system processes. This parameter cannot be changed.|
332
-
|`maxmemory-policy`|`noeviction`| Maxmemory policy is the setting used by the Redis server to select what to remove when `maxmemory` (the size of the cache that you selected when you created the cache) is reached. With Azure Managed Redis, the default setting is `noeviction`. This setting returns an error message if you attempt to insert data into a full Redis instance. This setting can be configured in the Azure portal. For more information, see [Memory policies](#memory-policies). |
333
-
|`maxmemory-samples`|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. |
334
-
|`lua-time-limit`|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. |
335
-
|`lua-event-limit`|500 |Max size of script event queue. |
336
-
|`client-output-buffer-limit normal` / `client-output-buffer-limit pubsub`|`0 0 0` / `32mb 8mb 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](https://redis.io/topics/clients). |
337
-
338
-
> [!NOTE]
339
-
> Azure Managed Redis only supports a subset of Redis configuration settings. Some of the most commonly used configuration settings, such as such as **max-memory-policy**, are configurable through the Azure portal or command-line management tools such as Azure CLI or PowerShell.
340
-
> Other values may be configured using the `CONFIG SET` command. See [Compatibility with Redis Community Edition configuration settings](https://redis.io/docs/latest/operate/rs/references/compatibility/config-settings/) for more information.
341
-
>
342
-
343
246
### Databases
344
247
345
248
Currently, Azure Managed Redis only supports a single database per instance.
0 commit comments