Release Notes and Announcements

Release Notes

Announcements

User Tutorial

Product Introduction

Overview

Product Strengths

Use Cases

Storage Engine

Product Series

Product Versions

Specifications and Performance

Read/Write Separation

Multi-AZ Deployment

Regions and AZs

Terms

Service Regions and Service Providers

Purchase Guide

Billing Overview

Pricing Center

Instance Purchasing

Renewal (Yearly/Monthly Subscription)

Refund (Yearly/Monthly Subscription)

Overdue Payments

Switching from Pay-as-You-Go to Yearly/Monthly Subscription

Getting Started

Quickly Creating an Instance

Connecting to Redis Instance

Operation Guide

Operation Overview

Connecting to a Database Instance

Managing Instances

Upgrade Instance

Management Node (Redis/ValKey Edition)

Multi-AZ Deployment Management

Backup and Restoration

Managing Accounts

Parameter Configuration

Slow Query

Access Management

Network and Security

Monitoring and Alarms

Event Management (Redis/ValKey Edition)

Data Migration

Global Replication for Redis Edition

Performance Optimization

Sentinel Mode

Development Guidelines

Naming Rules

Basic Usage Guidelines

Design Principles of Key and Value

Command Usage Guidelines

Design Principles of Client Programs

Connection Pool Configuration

Command Reference

Command Reference Overview

Redis Edition and Valkey Edition Command Compatibility

Version Command Usage Differences

Differences Between the Proxy Architecture and Direct Connection Mode

More Command Operations (Redis/Valkey Edition)

Memcached Edition Command Compatibility

Practical Tutorial

Building TencentDB for Redis® Client Monitoring Based on Spring Boot

Redis Client Connection Configuration Policy and Practice

Global SCAN Guide for Cluster Architecture

Eliminating Instances Securely

Hot Key and Big Key

AZ Migration Scheme

Troubleshooting

Connection Exception

Exception Analysis and Solution of Redisson Client Timeout Reconnection

Performance Troubleshooting and Fine-Tuning

API Documentation

History

Introduction

API Category

Making API Requests

Instance APIs

Parameter Management APIs

Other APIs

Backup and Restoration APIs

Region APIs

Monitoring and Management APIs

Log APIs

Data Types

Error Codes

FAQs

General

Connection and Login

Purchase

Service Agreement

Service Level Agreement

Glossary

Command Reference Overview

PDF

Focus Mode

Font Size

Last updated: 2026-03-17 20:46:27

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 versions do not support the RESP3 protocol.
The Valkey edition is fully compatible with all Redis 7.0 commands, ensuring seamless migration without requiring any modifications to existing application code.
Command Type
Description
Unsupported commands
This refers to commands from community editions that are not supported by Tencent Cloud Distributed Cache, which returns(error) ERR unknown command 'keys' message. The supported commands vary by version. For more information on the commands supported by different versions and architectures, see Overview.
Partially supported commands
Cluster Architecture is compatible with smart clients such as JedisCluster. For compatibility with JedisCluster, Tencent Cloud Distributed Cache 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
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
Cluster Architecture supports multiple databases (256 by default); therefore, it can support all commands related to database operations.

Help and Support

Was this page helpful?

You can also Contact sales or Submit a Ticket for help.

Help us improve! Rate your documentation experience in 5 mins.

Feedback

tencent cloud

Tencent Cloud Distributed Cache (Redis OSS-Compatible)

Command Reference Overview

Help and Support

Command Type	Description
Unsupported commands	This refers to commands from community editions that are not supported by Tencent Cloud Distributed Cache, which returns`(error) ERR unknown command 'keys'` message. The supported commands vary by version. For more information on the commands supported by different versions and architectures, see Overview.
Partially supported commands	Cluster Architecture is compatible with smart clients such as JedisCluster. For compatibility with JedisCluster, Tencent Cloud Distributed Cache 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	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	Cluster Architecture supports multiple databases (256 by default); therefore, it can support all commands related to database operations.