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.
@@ -33,7 +35,6 @@ Although we don't own or support any client libraries, we do recommend some libr
33
35
For information on client library-specific guidance best practices, see the following links:
@@ -35,7 +35,7 @@ All client libraries work with your Redis instance with Enterprise clustering po
35
35
36
36
## Blocked commands
37
37
38
-
Configuration and management of Azure Managed Redis instances is managed by Microsoft, which disables the following commands by default.
38
+
Configuration and management of Azure Managed Redis instances is managed by Microsoft, which disables the following commands by default.
39
39
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
@@ -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:
0 commit comments