Berita Terkini dan Pengumuman

Catatan Rilis

Pengumuman

Pengenalan Produk

Ikhtisar

Keunggulan

Kasus Penggunaan

Mesin Penyimpanan

Product Series

Performa

Pemisahan Baca/Tulis

Deployment Multi-AZ

Wilayah dan AZ

Panduan Pembelian

Ikhtisar Penagihan

Metode Pembelian

Pembayaran Jatuh Tempo

Memulai

Membuat Instans TencentDB for Redis

Menghubungkan ke Instans TencentDB for Redis (melalui Jaringan Pribadi)

Panduan Pengoperasian

Ikhtisar Operasi

Koneksi SDK

Manajemen dan Pemeliharaan Instans

Peningkatan Instans

Manajemen Deployment Multi-AZ

Pencadangan dan Pemulihan

Manajemen akun

Konfigurasi Parameter

Manajemen Akses

Jaringan dan Keamanan

Pemantauan dan Peringatan Alarm

Replikasi Global

Service Agreement

Service Level Agreement

Glosarium

Overview

Mode fokus

Ukuran font

Terakhir diperbarui: 2026-03-17 18:23:48

In the high availability architecture of TencentDB for Redis®, the backend ensures service continuity (such as automatic recovery after physical server downtime or network jitter) through a second-level failover mechanism. The robustness of the client connection pool becomes a key bottleneck affecting business availability.
Fault Type
Business Scenario
TencentDB for Redis® Processing Mechanism
Challenge for Client
Impact on Business
Active switchover
Compatible version upgrade, proxy version upgrade, and data migration.
It actively sends RST to reset the connection.
Detect interruption and reconnect it quickly.
Temporary jitter exists and can be quickly restored.
Passive switchover
The physical server crashes unexpectedly.
It does not actively send RST to reset the connection.
Existing connections become "dead connections", which can be removed relying on the client's keepalive mechanism.
Recovery delay depends on the keepalive efficiency of the connection pool.
To resolve the above issues, this solution provides a configuration policy for the client connection pool. Through client-side optimization, it reduces business unavailability time caused by passive switchovers from minutes to seconds, aligning with Tencent Cloud's service recovery capability.

Bantuan dan Dukungan

Apakah halaman ini membantu?

Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.

masukan

tencent cloud

Tencent Cloud Distributed Cache (Redis OSS-Compatible)

Overview

Bantuan dan Dukungan

Fault Type	Business Scenario	TencentDB for Redis^® Processing Mechanism	Challenge for Client	Impact on Business
Active switchover	Compatible version upgrade, proxy version upgrade, and data migration.	It actively sends RST to reset the connection.	Detect interruption and reconnect it quickly.	Temporary jitter exists and can be quickly restored.
Passive switchover	The physical server crashes unexpectedly.	It does not actively send RST to reset the connection.	Existing connections become "dead connections", which can be removed relying on the client's keepalive mechanism.	Recovery delay depends on the keepalive efficiency of the connection pool.