Tencent Cloud

Recent Pages

Overview

最終更新日:2024-11-05 10:22:22

Memory Edition (Cluster Architecture) stores data in a distributed manner, and its biggest difference from standard architecture lies in whether a single command supports multikey access. For the cluster architecture, commands can be categorized into partially supported, custom, and unsupported as detailed below:
Note:
The current Redis 7.0 and 6.2 do not support the RESP3 protocol.
Command Type
Description
Unsupported commands
(error) ERR unknown command 'keys' will be returned for unsupported commands. For more information on the commands supported by different versions and architectures, see Overview.
Partially supported commands
Memory Edition (Cluster Architecture) is compatible with smart clients such as JedisCluster. For compatibility with JedisCluster, TencentDB for Redis® modifies the IP list returned by the supported commands, and the IP address of each node in the returned information is the instance's VIP. For more information, see Use Case of Partially Supported Commands.
Supported cross-slot commands
The in-memory version (cluster architecture) currently supports cross-Slot access commands, including MGET, MSET, DEL, Hset, Scan, Keys. However, cross-Slot access for other multi-KEY commands is not yet supported.
Custom commands
Custom commands support the access of each node in a cluster. A new parameter Node ID is added to the right of the parameter list of the original command, including INFO, MEMORY, SLOWLOG, FLUSHDB, PING, and KEYS (with hashtag supported for preferred match). For more information, see Use Cases of Custom Commands.
Supported DMC commands
Database Management Center (DMC) allows you to log in to your TencentDB instances to access them, view their key metric information, and run Redis commands. For more information, see List of Supported DMC Commands.
Transactional commands
Memory Edition (Cluster Architecture) supports transactional commands provided that the transactions are started by the WATCH command. The keys of a transaction should be stored in the same slot, and the keys of WATCH and transaction-related keys should also be stored in the same slot. Hashtag is recommended for multikey transactions in cluster mode.
Multi-database commands
Memory Edition (Cluster Architecture) supports multiple databases (256 by default); therefore, it can support all commands related to database operations.

お問い合わせ

カスタマーサービスをご提供できるため、ぜひお気軽にお問い合わせくださいませ。

テクニカルサポート

さらにサポートが必要な場合は、サポートチケットを送信して弊社サポートチームにお問い合わせください。24時間365日のサポートをご提供します。

電話サポート（24 時間365日対応）

tencent cloud

Recent Pages

Overview

この記事はお役に立ちましたか？

この記事はお役に立ちましたか？

Command Type	Description
Unsupported commands	`(error) ERR unknown command 'keys'` will be returned for unsupported commands. For more information on the commands supported by different versions and architectures, see Overview.
Partially supported commands	Memory Edition (Cluster Architecture) is compatible with smart clients such as JedisCluster. For compatibility with JedisCluster, TencentDB for Redis^® modifies the IP list returned by the supported commands, and the IP address of each node in the returned information is the instance's VIP. For more information, see Use Case of Partially Supported Commands.
Supported cross-slot commands	The in-memory version (cluster architecture) currently supports cross-Slot access commands, including MGET, MSET, DEL, Hset, Scan, Keys. However, cross-Slot access for other multi-KEY commands is not yet supported.
Custom commands	Custom commands support the access of each node in a cluster. A new parameter Node ID is added to the right of the parameter list of the original command, including `INFO`, `MEMORY`, `SLOWLOG`, `FLUSHDB`, `PING`, and `KEYS` (with hashtag supported for preferred match). For more information, see Use Cases of Custom Commands.
Supported DMC commands	Database Management Center (DMC) allows you to log in to your TencentDB instances to access them, view their key metric information, and run Redis commands. For more information, see List of Supported DMC Commands.
Transactional commands	Memory Edition (Cluster Architecture) supports transactional commands provided that the transactions are started by the `WATCH` command. The keys of a transaction should be stored in the same slot, and the keys of `WATCH` and transaction-related keys should also be stored in the same slot. Hashtag is recommended for multikey transactions in cluster mode.
Multi-database commands	Memory Edition (Cluster Architecture) supports multiple databases (256 by default); therefore, it can support all commands related to database operations.

tencent cloud

サインアップ

ログイン

Recent Pages

Overview

この記事はお役に立ちましたか？

この記事はお役に立ちましたか？