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
文档Tencent Cloud Distributed Cache (Redis OSS-Compatible)

Adding Replicas to Multi-AZ Deployed Instance

聚焦模式
字号
最后更新时间: 2026-03-17 17:45:58

Overview

A multi-AZ deployed instance uses the one-replica architecture by default. One master node and two replica nodes are recommended, with the master node and one replica node deployed in the master AZ and the other replica node deployed in the replica AZ. This deployment mode maximizes the service availability and greatly reduces the delay caused by failures of the master node. If the master node fails, the replica node in the master AZ can be first elected as the new master node, ensuring that the access latency in the master AZ will not be affected by the switch of the master node to the replica AZ otherwise. For more information, see Multi-AZ Deployment. We recommend you select the number of replicas based on your business needs.

Billing Description

Pay-as-you-go: The instance will be billed based on the new specification on the next hour under tier 1, and fees will be settled on each hour. For pricing details, see Pricing.

Notes

If the number of replicas is increased, the instance will be charged at the price of the new specification.
Increasing the number of replicas will not cause momentary disconnections or command execution failures or affect existing connections.

Prerequisites

The database is on v4.0 or later.
The instance is in Running status.

Directions

2. Above the instance list on the right, select the region.
3. In the instance list, find the target instance.
4. In the Operation column of the target instance, select Configure > Add Replica.
5. In the TencentDB for Redis® Configuration Changes pop-up window, select the number of replicas to be added from the Add Replica drop-down list. Then, select AZs for them in the AZ drop-down list. The parameters are as described below.
Parameter
Description
Used Capacity
Capacity used by the current instance.
Min Memory
Minimum memory specification of the current instance required to prevent the disk space from being used up.
Add Replica
Specify the number of replicas to be added based on the required security level of your business data.
AZ
Specify AZs for the added replicas. For more information on how to configure this parameter, see Multi-AZ Deployment.
Compare
Comparison of the specification before and after adding replicas. Check whether the new configuration meets your expectations.
Configuration Change Fee
Make sure that you understand the billing information of the new configuration. The hourly rate of the new configuration will be displayed for pay-as-you-go instances.

6. After completing the configuration, click OK. Then, the instance status will change to Processing. Wait for the status to become Running.
API
Description
Upgrades instance specification, including the shard size, shard quantity, and replica quantity.

帮助和支持

本页内容是否解决了您的问题?

填写满意度调查问卷,共创更好文档体验。

文档反馈