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

Accessing Multi-AZ Deployed Instances

PDF
Focus Mode
Font Size
Last updated: 2026-03-17 17:45:57
Tencent Cloud Distributed Cache provides the same access method for both multi-AZ instances and single-AZ instances, offering a private IPv4 address to facilitate client access to the database instance.

Private IPv4 address

A Tencent Cloud Distributed Cache instance has primary/secondary nodes deployed in different AZs, enabling cross-AZ deployment. Subnets in different AZs can be created under the same VPC, and subnets in different AZs are interconnected via the private network by default. The system assigns it a private IPv4 address based on the VPC selected for the instance, and clients can access the instance via this private IPv4 address across the entire region.
The private IPv4 address can mask the failure switchover of the Tencent Cloud Distributed Cache service. When a service node of the Tencent Cloud Distributed Cache fails and triggers a primary-secondary switchover, Tencent Cloud Distributed Cache will automatically update the backend service processes associated with the private IPv4 address in the background, so applications do not need to change the private IPv4 address.

Viewing the private IP of an instance

Log in to the Tencent Cloud Distributed Cache console, and in the Network column of the instance list, you can view the private IPv4 address assigned to the instance.
In instance list, click Instance ID to go to the management page. On the Instance Details page, in the Network Info section, you can view the instance's Private IPv4 Address.


Accessing a multi-AZ deployed instance

Use the multi-language SDK to access a Tencent Cloud Distributed Cache instance. For specific operations, see Connecting to an instance.
In the case of multiple AZ deployment, to reduce latency for business access to the Tencent Cloud Distributed Cache service, Tencent Cloud Distributed Cache provides the capability of proximity access. For specific operations, see Proximity Access.

Help and Support

Was this page helpful?

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

Feedback