Tencent Cloud Distributed Cache (Redis-compatible) is fully compatible with the Redis protocol and supports most native commands from the community edition. From a global perspective, this document summarizes the support status of each command family, usage differences under the cluster architecture, and module commands exclusive to the Valkey edition, helping you quickly locate compatibility information for the commands you need.
Command Family Index
The table below lists all command families supported by the product. You can jump to the corresponding detailed documentation as needed to view the version support status of specific commands.
|
Strings | String storage, retrieval, and bitwise operations | All versions | |
Hash | Operations on key-value pair collections | All versions | |
List | Operations on doubly linked lists | All versions | |
Sets | Operations on unordered sets | All versions | |
Sorted Sets | Operations on sorted sets | All versions | |
Keys | General key management operations | All versions | |
Bitmap | Operations on bit arrays | All versions | |
HyperLogLog | Cardinality estimation | All versions | |
Geo | Geospatial operations | Redis 4.0+ | |
Stream | Operations on message streams | Redis 5.0+ | |
Pub/Sub | Publish/subscribe messaging | All versions | |
Scripting | Execution of Lua scripts | All versions | |
Transactions | Transaction operation | All versions | |
Server | Server management commands | All versions | |
Connection | Connection management commands | All versions | |
Cluster | Cluster management commands | Redis 4.0+ (cluster architecture) | |
Valkey Edition Module Commands
The following command families are exclusive extension modules for the Valkey engine and are supported only by Valkey version 8.0 and above.
|
JSON Module | Storage, retrieval, and path operations for JSON documents | Valkey 8.0+ | |
Bloom Filter Module | Bloom filter (probabilistic duplicate detection) | Valkey 8.0+ | |
Search Module | Full-text search and vector search | Valkey 9.0+ | |
Cluster Architecture Command Usage Instructions
The cluster architecture provides a user experience consistent with the standard architecture through the Proxy layer. However, because the underlying data is distributed across multiple shard nodes by Slot, the behavior of some commands differs from that in the standard architecture.
Cross-Slot Commands
In the cluster architecture, data is distributed across 16384 Slots based on the CRC16 value of the Key. Commands involving multiple Keys are categorized into two types according to their cross-Slot support.
|
Cross-slot support | The Proxy layer automatically splits requests and aggregates results, with no awareness required from the business logic. | MGET,MSET,DEL |
Cross-slot not supported | All keys involved in the operation must reside in the same Slot; otherwise, an error is returned. Hash tags can be used to avoid this. | RENAME, MSETNX, SDIFF, SUNION, SINTER, ZINTERSTORE, and so on. |
Note:
For commands that do not support cross-Slot operations, you can use Hash Tags (which route Keys with the same {tag} portion to the same Slot) to bypass this limitation. For example, {user}.name and {user}.age will be routed to the same Slot.
Custom commands
In the cluster architecture, commands such as INFO, SLOWLOG, SCAN, KEYS, PING, and FLUSHDB are executed by default at the Proxy layer or randomly routed to a shard. To execute a command on a specific shard node, append the node ID parameter to the end of the command:
COMMAND arg1 arg2 ... [node ID]
You can view the node ID on the console' s node management page or obtain it via the CLUSTER NODES command. Note:
For Proxy version 5.5.0 and later, the node ID parameter is no longer required for custom commands, as the Proxy automatically handles routing. For specific usage, see the Custom Command Usage Example. Limited support commands
The cluster architecture provides services externally through the Proxy layer, hiding the actual network topology of the backend shards. To ensure compatibility with smart clients such as Jedis Cluster and Lettuce Cluster, the following Cluster commands can be executed normally. However, the node IP addresses returned are uniformly replaced with the instance's Proxy VIP address (that is, the instance's private IPv4 access address). For details, see the Redis/Valkey Edition Partially Supported Commands Usage Example. |
CLUSTER NODES | The returned node IP address is the instance Proxy VIP, not the real IP address of the backend shard. |
CLUSTER SLOTS | The returned node IP address is the instance Proxy VIP, not the real IP address of the backend shard. |
CLUSTER SHARDS | In Redis 7.0+/Valkey 8.0+, the returned node IP address is the instance Proxy VIP, not the real IP address of the backend shard. |
Transaction support
The cluster architecture supports transactions (MULTI/EXEC), but the following conditions must be met:
All Keys involved in a transaction must reside in the same Slot. It is recommended to use Hash Tags (such as {user}.name and {user}.age) to route the related Keys to the same Slot.
If you use the WATCH command to implement optimistic locking, the Keys being monitored and the Keys operated on within the transaction must also reside in the same Slot.
Multi-DB Support
The cluster architecture supports multiple DBs (switched via the SELECT command) and provides a total of 256 DBs (DB 0 ~ DB 255).
The command is not supported
Due to security, architectural compatibility, or feature limitations, the following commands are not supported for execution in the product and will return an error when invoked:
System Management: BGREWRITEAOF, BGSAVE, CONFIG, DEBUG, and CLUSTER write operations (such as ADDSLOTS / FAILOVER / RESET)
Dangerous Operations: FLUSHALL (available in standard architecture), SHUTDOWN, SLAVEOF / REPLICAOF
Protocol Layer: HELLO (RESP3 protocol)
Access Control: ACL series commands
Module Management: MODULE LOAD / UNLOAD
Version Differences and Considerations
Command behavior varies across different engine versions, primarily involving Lua script sandbox restrictions and command return value changes. Before performing a version upgrade, it is recommended to thoroughly understand the changes in the target version to avoid impacting your business. For specific information, see Major Version Command Usage Differences. References
|
| Detailed support status for each command family across different versions and architectures |
| Command behavior changes across Redis versions 5.0 → 6.2 → 7.0 / Valkey 8.0+ |
| Usage of commands with limited support, such as CLUSTER NODES / CLUSTER SLOTS |
| Custom usage of commands such as INFO, SLOWLOG, and SCAN in cluster architecture |
| Commands executable in the DMC database management tool |
| Differences in command support between Proxy mode and direct connection mode |