tencent cloud

Tencent Cloud Distributed Cache (Redis OSS-Compatible)

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
Database Audit
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
Terms of Service
Glossary
Contact Us

Cluster Architecture

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2026-03-17 16:36:34

Architecture Overview

The cluster architecture is a distributed version built based on the Redis Community Edition. It is compatible with Redis 4.0, 5.0, 6.2, and 7.0, as well as Valkey 8.0 protocols. It adopts a distributed sharding design and supports horizontal scaling from 1 to 128 shards and vertical scaling from 1 to 5 replicas, delivering high performance of tens of millions of QPS. Capacity expansion, capacity reduction, and migration processes have minimal impact on businesses, ensuring high service availability. For specific performance data, see Specifications and Performance.


Core Components

Component
Description
Shard
The smallest data storage unit, consisting of a group of master and replica nodes. The cluster evenly distributes 16,384 hash slots across shards. Each shard stores data for its assigned slots and supports online data balancing and migration.
Master node
The node within a shard responsible for handling read/write requests and synchronizing data to replica nodes. Each shard has one master node.
Replica node
A node within a shard responsible for data redundancy and high availability. It synchronizes data from the master node in real time and automatically takes over as the new master node upon master node failure.
Proxy
A built-in proxy component that receives client requests and routes them to the corresponding shards. It provides load balancing, read/write separation, and cross-shard command processing capabilities, shielding cluster topology details from clients.

Shard and Replica Configuration

A larger number of shards provides higher capacity and performance. All shards participate in data storage and request processing. When the number of shards is greater than or equal to 1, data is automatically distributed based on hash slots, enabling horizontal scaling of storage capacity and throughput.
A larger number of replicas provides higher availability. All replica nodes participate in high-availability failover. When the number of replicas is greater than or equal to 1, you can enable the read/write separation feature to vertically scale read performance. For more information, see Read/Write Separation.
Note:
Commands that span multiple hash slots have certain compatibility limitations. For details, see Command Reference Overview.
Configuration Item
Optional Specifications
Shard specifications (GB):
1, 2, 4, 8, 12, 16, 20, 24, 32, 40, 48, and 64
Shard quantity
1, 3, 5, 8, 12, 16, 24, 32, 40, 48, 64, 80, 96, and 128
Replica quantity
1, 2, 3, 4, and 5

Upper Limits of Specifications

Item
Upper Limit
Description
Total storage capacity
8TB
128 shards x 64 GB
Concurrent performance
Tens of millions of QPS
Tencent Cloud conducts multiple stress tests in standard testing environments and uses stable values as official references. For details, see Specifications and Performance.

도움말 및 지원

문제 해결에 도움이 되었나요?

피드백