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
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

Configuring Multi-AZ Deployment

PDF
Focus Mode
Font Size
Last updated: 2026-03-17 17:45:57
This article introduces how to configure and view multiple AZs through the Tencent Cloud Distributed Cache console.

Overview

Tencent Cloud Distributed Cache supports deploying replicas across multiple AZs within the same region. Compared to single-AZ instances (where the master node and replica nodes reside in the same AZ), multi-AZ instances deliver higher availability and disaster recovery capabilities.
For instances where read-only replica (read/write separation) is not enabled, both read and write requests are routed through the Proxy in the same AZ to the master node, ensuring data consistency while guaranteeing at most one cross-AZ (Availability Zone) access.
Read/Write separation enabled (that is, replicas can only be read from): Write requests are routed by proxy to the master node, but read requests are routed to the replica node in the same AZ as the proxy, so that read requests can get responded by the nearest node.
We recommend that you deploy one master node and one replica node in the master AZ, and another replica node in the replica AZ. If the master node fails, the replica node in the master AZ can be promoted quickly to avoid cross-AZ master-replica switch. Such a deployment solution can maximize service availability and reduce the delay caused by master node failures.

Configuring multi-AZ deployment

2. Select parameters such as billing mode, region, product edition, compatible version, architecture version, and memory capacity.
Note:
For details about regions, see Regions and AZs.
For specific information, see Creating an Instance.
3. The replica quantity determines the maximum number of AZs, which is the replica quantity plus 1. Select a value based on your actual business needs.
Note:
Distributed Cache supports deploying a maximum of 6 AZs within the same region.
4. When configuring AZ, select Multi-AZ Deployment and set the AZs of the master and replica nodes.

5. Set information such as network, port, parameter template, instance name, and password.
6. Confirm the price. After making the payment, return to the instance list. After the status of the instance changes to Running, it can be used normally.
Log in to Distributed Cache console, in the instance list's AZ column, the instance with the

icon is a multi-AZ instance, and you can view multi-AZ information.
In the Instance List, click the Instance ID to go to the management page. On the Instance Details page, the instance with the

icon at the AZ location is a multi-AZ instance, and you can view multi-AZ information.
In the Instance List, click the Instance ID to go to the management page. On the Node Management page, you can view detailed information of each node in different AZs.

Related APIs

API
Feature Description
Creates an instance (the

Help and Support

Was this page helpful?

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

Feedback