Skip to content

Commit 900765a

Browse files
committed
fix link, acrolinx
1 parent 34dc8a4 commit 900765a

File tree

1 file changed

+17
-10
lines changed

1 file changed

+17
-10
lines changed

articles/redis/configure.md

Lines changed: 17 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ You can view and configure the following settings using the **Resource Menu**.
2727
- [Settings](#settings)
2828
- [Authentication](#authentication)
2929
- [Advanced settings](#advanced-settings)
30-
- [Data persistence](#data-persistence-preview)
30+
- [Data persistence](#data-persistence-preview)
3131
- [Encryption](#encryption)
3232
- [Active geo-replication](#active-geo-replication)
3333
- [Scale](#scale-preview)
@@ -76,15 +76,16 @@ The **Settings** section allows you to access and configure the following settin
7676

7777
- [Authentication](#authentication)
7878
- [Advanced settings](#advanced-settings)
79+
- [Data persistence](#data-persistence-preview) (preview)
7980
- [Encryption](#encryption)
8081
- [Active geo-replication](#active-geo-replication)
81-
- [Scale](#scale)
82+
- [Scale](#scale-preview)
8283
- [Properties](#properties)
8384
- [Locks](#locks)
8485

8586
### Authentication
8687

87-
You have two options for authentication: access keys and [Microsoft Entra Authentication](entra-for-authentication.md). Using Microsoft Entra Authentication is recommended because it is more secure.
88+
You have two options for authentication: access keys and [Microsoft Entra Authentication](entra-for-authentication.md). Using Microsoft Entra Authentication is recommended because it's more secure.
8889

8990
#### [Access keys](#tab/access-keys)
9091

@@ -102,11 +103,15 @@ Select **Microsoft Entra Authentication** to a password-free authentication mec
102103

103104
### Advanced settings
104105

105-
The following settings are configured on the **Advanced settings** on the left.
106+
The following properties are set:
107+
108+
- Non-TLS access only
109+
- Eviction Policy
110+
- Defer Redis DB version updates
106111

107112
### Data persistence (preview)
108113

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.
114+
Use **Data persistence** to enable, disable, or configure data persistence for your Redis cache. Azures Managed Redis offers Redis persistence using either RDB persistence or AOF persistence.
110115

111116
For more information, see [Configure data persistence for an Azure Managed Redis instance](how-to-persistence.md).
112117

@@ -234,7 +239,7 @@ The settings in the **Help** section provide you with options for resolving issu
234239

235240
### Resource health
236241

237-
**Resource health** watches your resource and tells you if it's running as expected. Resource health is not yet supported for Azure Managed Redis.
242+
**Resource health** watches your resource and tells you if it's running as expected. Resource health isn't yet supported for Azure Managed Redis.
238243
For more information about the Azure Resource health service, see [Azure Resource health overview](/azure/service-health/resource-health-overview).
239244

240245
### Support and Troubleshooting
@@ -243,6 +248,8 @@ Select **Support + Troubleshooting** to open a support request for your cache.
243248

244249
## Other configuration information
245250

251+
Here's some additional information about Azure Managed Redis caches.
252+
246253
### Databases
247254

248255
Currently, Azure Managed Redis only supports a single database per instance.
@@ -254,13 +261,13 @@ The `maxclients` property is different for each Azure Managed Redis SKU.
254261
See the [Azure Managed Redis pricing page](https://aka.ms/amrpricing) for more information about the connection limits per SKU.
255262

256263
> [!NOTE]
257-
> 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.
264+
> Each cache size allows *up to* some number connections, but each connection adds overhead. Examples of such overhead include CPU and memory usage due to TLS/SSL encryption. The maximum connection limit for a cache size assumes a lightly loaded cache. If the load from connection overhead *plus* the load from client operations exceeds the system's capacity, the cache might encounter capacity issues even without exceeding the connection limit for the current cache size.
258265
>
259266
260267
### Redis commands not supported in Azure Managed Redis
261268

262-
Configuration and management of Azure Managed Redis instances is managed by Microsoft, which disables several commands in order to ensure safe and consistent operation of the service.
263-
If you try to invoke them, you receive an error message similar to `"(error) ERR unknown command"`.
269+
Microsoft manages the configuration and management of Azure Managed Redis instances, which disables several commands in order to ensure safe and consistent operation of the service.
270+
If you try to invoke a disabled command, you receive an error message similar to `"(error) ERR unknown command"`.
264271

265272
Blocked commands include:
266273

@@ -271,7 +278,7 @@ Blocked commands include:
271278
- MOVE
272279
- PSYNC
273280
- REPLICAOF
274-
- REPLCONF - Azure Managed Redis instances don't allow customers to add external replicas. This [command](https://redis.io/commands/replconf/) is normally only sent by servers.
281+
- REPLCONF - Azure Managed Redis instances don't allow customers to add external replicas. Normally, only servers send this command.
275282
- SAVE
276283
- SHUTDOWN
277284
- SELECT

0 commit comments

Comments
 (0)