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
Azure Cache for Redis is based on the popular open-source in-memory data store, open-source Redis. Azure Cache for Redis can be accessed by a wide variety of Redis clients for many programming languages. Each client library has its own API that makes calls to Redis server using Redis commands, but the client libraries are built to talk to any Redis server.
13
+
Azure Cache for Redis is based on the popular open-source in-memory data store, open-source Redis. Redis clients for many programming languages can access Azure Managed Redis. Each client library has its own API that makes calls to Redis server using Redis commands, but the client libraries are built to talk to any Redis server.
14
14
15
15
Each client maintains its own reference documentation for its library. The clients also provide links to get support through the client library developer community. The Azure Cache for Redis team doesn't own the development, or the support for any client libraries.
16
16
@@ -33,7 +33,6 @@ Although we don't own or support any client libraries, we do recommend some libr
33
33
For information on client library-specific guidance best practices, see the following links:
@@ -48,9 +47,9 @@ We _recommend_ you use redisson 3.14.1 or higher. Older versions contain known
48
47
49
48
Other notes:
50
49
51
-
- Redisson defaults to 'read from replica' strategy, unlike some other clients. To change this, modify the 'readMode' config setting.
52
-
- Redisson has a connection pooling strategy with configurable minimum and maximum settings, and the default minimum values are large. The large defaults could contribute to aggressive reconnect behaviors or 'connection storms'. To reduce the risk, consider using fewer connections because you can efficiently pipeline commands, or batches of commands, over a few connections.
53
-
- Redisson has a default idle connection timeout of 10 seconds, which leads to more closing and reopening of connections than ideal.
50
+
- Redisson defaults to 'read from replica' strategy, unlike some other clients. To change this default, modify the 'readMode' config setting.
51
+
- Redisson has a connection pooling strategy with configurable minimum and maximum settings, and the default minimum values are large. The large defaults could contribute to aggressive reconnect behaviors or 'connection storms.' To reduce the risk, consider using fewer connections because you can efficiently pipeline commands, or batches of commands, over a few connections.
52
+
- Redisson has a default idle connection time out of 10 seconds, which leads to more closing and reopening of connections than ideal.
54
53
55
54
Here's a recommended baseline configuration for cluster mode that you can modify as needed:
56
55
@@ -83,7 +82,7 @@ clusterServersConfig:
83
82
tcpNoDelay: true
84
83
```
85
84
86
-
For an article demonstrating how to use Redisson's support for JCache as the store for HTTP session state in IBM Liberty on Azure, see [Use Java EE JCache with Open Liberty or WebSphere Liberty on an Azure Kubernetes Service (AKS) cluster](/azure/developer/java/ee/how-to-deploy-java-liberty-jcache).
85
+
For an article about Redisson's support for JCache as the store for HTTP session state in IBM Liberty on Azure, see [Use Java EE JCache with Open Liberty or WebSphere Liberty on an Azure Kubernetes Service (AKS) cluster](/azure/developer/java/ee/how-to-deploy-java-liberty-jcache).
Azure Managed Redis (preview) is based on the popular in-memory data store, Redis. Azure Managed Redis can be accessed by a wide variety of Redis clients for many programming languages. Each client library has its own API that makes calls to Redis server using Redis commands, but the client libraries are built to talk to any Redis server.
13
+
Azure Managed Redis (preview) is based on the popular in-memory data store, Redis. Redis clients for many programming languages can access Azure Managed Redis. Each client library has its own API that makes calls to Redis server using Redis commands, but the client libraries are built to talk to any Redis server.
14
14
15
15
Each client library maintains its own reference documentation. The libraries also provide links to get support through the client library developer community. The Azure Managed Redis team doesn't own the development, or the support for any client libraries.
16
16
17
-
Recommendations below are based on popularity and whether there's an active online community to support and answer your questions. We only recommend using the latest available version, and upgrading regularly as new versions become available. These libraries are under active development and often release new versions with improvements to reliability and performance.
17
+
The following recommendations are based on popularity and whether there's an active online community to support and answer your questions. We only recommend using the latest available version, and upgrading regularly as new versions become available. These libraries are under active development and often release new versions with improvements to reliability and performance.
@@ -31,12 +31,12 @@ Recommendations below are based on popularity and whether there's an active onli
31
31
## Choosing the right client library based on your clustering policy
32
32
33
33
Azure Managed Redis supports the Enterprise clustering policy and the OSS clustering policy. See more information here (add link to clustering policy information).
34
-
All client libraries work with your Redis instance with Enterprise clustering policy. However, if you are using the OSS clustering policy, ensure that the client library you choose supports connecting to clustered Redis instances.
34
+
35
+
All client libraries work with your Redis instance with Enterprise clustering policy. However, if you're using the OSS clustering policy, ensure that the client library you choose supports connecting to clustered Redis instances.
35
36
36
37
## Blocked commands
37
38
38
-
Configuration and management of Azure Managed Redis instances is managed by Microsoft, which disables the following commands by default.
39
-
For more information on blocked commands, see [Cluster management commands compatibility](https://redis.io/docs/latest/operate/rs/references/compatibility/commands/cluster/)
39
+
Microsoft manages the configuration and management of Azure Managed Redis instances, which disables the following commands by default. For more information on blocked commands, see [Cluster management commands compatibility](https://redis.io/docs/latest/operate/rs/references/compatibility/commands/cluster/)
40
40
41
41
### Multi-key commands
42
42
@@ -47,22 +47,23 @@ You might also see `CROSSSLOT` errors with Enterprise clustering policy. Only th
47
47
In Active-Active databases, multi-key write commands (`DEL`, `MSET`, `UNLINK`) can only be run on keys that are in the same slot. However, the following multi-key commands are allowed across slots in Active-Active databases: `MGET`, `EXISTS`, and `TOUCH`. For more information, see [Database clustering](https://redis.io/docs/latest/operate/rs/databases/durability-ha/clustering/#multikey-operations).
48
48
49
49
### Commands blocked for Enterprise clustering policy
50
-
* CLUSTER INFO
51
-
* CLUSTER HELP
52
-
* CLUSTER KEYSLOT
53
-
* CLUSTER NODES
54
-
* CLUSTER SLOTS
50
+
51
+
- CLUSTER INFO
52
+
- CLUSTER HELP
53
+
- CLUSTER KEYSLOT
54
+
- CLUSTER NODES
55
+
- CLUSTER SLOTS
55
56
56
57
### Commands blocked for active geo-replication
57
-
* FLUSHALL
58
-
* FLUSHDB
58
+
59
+
- FLUSHALL
60
+
- FLUSHDB
59
61
60
62
## Client library-specific guidance
61
63
62
64
For information on client library-specific guidance best practices, see the following links:
@@ -77,9 +78,9 @@ We _recommend_ you use redisson 3.14.1 or higher. Older versions contain known
77
78
78
79
Other notes:
79
80
80
-
- Redisson defaults to 'read from replica' strategy, unlike some other clients. To change this, modify the 'readMode' config setting.
81
-
- Redisson has a connection pooling strategy with configurable minimum and maximum settings, and the default minimum values are large. The large defaults could contribute to aggressive reconnect behaviors or 'connection storms'. To reduce the risk, consider using fewer connections because you can efficiently pipeline commands, or batches of commands, over a few connections.
82
-
- Redisson has a default idle connection timeout of 10 seconds, which leads to more closing and reopening of connections than ideal.
81
+
- Redisson defaults to 'read from replica' strategy, unlike some other clients. To change this default, modify the 'readMode' config setting.
82
+
- Redisson has a connection pooling strategy with configurable minimum and maximum settings, and the default minimum values are large. The large defaults could contribute to aggressive reconnect behaviors or 'connection storms.' To reduce the risk, consider using fewer connections because you can efficiently pipeline commands, or batches of commands, over a few connections.
83
+
- Redisson has a default idle connection time-out of 10 seconds, which leads to more closing and reopening of connections than ideal.
83
84
84
85
Here's a recommended baseline configuration for cluster mode that you can modify as needed:
85
86
@@ -112,7 +113,7 @@ clusterServersConfig:
112
113
tcpNoDelay: true
113
114
```
114
115
115
-
For an article demonstrating how to use Redisson's support for JCache as the store for HTTP session state in IBM Liberty on Azure, see [Use Java EE JCache with Open Liberty or WebSphere Liberty on an Azure Kubernetes Service (AKS) cluster](/azure/developer/java/ee/how-to-deploy-java-liberty-jcache).
116
+
For an article about Redisson's support for JCache as the store for HTTP session state in IBM Liberty on Azure, see [Use Java EE JCache with Open Liberty or WebSphere Liberty on an Azure Kubernetes Service (AKS) cluster](/azure/developer/java/ee/how-to-deploy-java-liberty-jcache).
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments