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

Upgrading Proxy

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

Overview

Distributed Cache releases minor version updates for Proxy periodically to enhance features or fix known issues.

Note on Upgrade

The system automatically detects the minor version of Proxy. If the proxy upgrade button is grayed out, it indicates that the instance is already the latest proxy version.
As the version release time varies by region, the minor version release status is as displayed in the console.

Upgrade Impact

The version upgrade process mainly consists of data sync and instance switch:
During data sync, the service will not be affected.
During data switch, the instance will experience transient disconnections lasting seconds and a read-only state for up to 1 minute (required for data synchronization). Ensure your application code has automatic reconnection capability.

Preparations for Upgrade

The instance to be upgraded is in
We recommend that you perform upgrade in the maintenance time during off-peak hours.

Upgrade Directions

1. Log in to the Distributed Cache console.
2. Above the instance list on the right, select the region.
3. In the instance list, find the target instance.
4. Click its instance ID to go to the Instance Details page.
5. In the Specs Info section on the Instance Details page, click Upgrade Proxy next to Proxy Version.

6. In the pop-up window, confirm the information of the target instance based on the following table, configure the target version, and click OK.

Parameter
Description
Instance ID
ID of the instance to be upgraded
Current Version
Current minor version of the proxy
Target Version
Target version after proxy upgrade. The target version cannot be selected.
Switch Time
Switch Now: The switch will be performed when the data sync is almost completed (the data left to be synced is less than 10 MB).
Switch in Maintenance Time: The switch will be performed during the instance maintenance time. If the switch conditions cannot be met in the current maintenance time, the switch will be attempted in the next maintenance time. You can modify the Maintenance Window on the instance details page.
7. Return to the instance list. After the Instance Status changes to Running, you can see that the instance version has been upgraded in the instance list or instance details.

Related APIs

API Name
Feature Description
Upgrades proxy version

도움말 및 지원

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

피드백