This document describes how to configure multiple AZs for your TencentDB for Redis instance and how to view them in the console.
Overview
You can now deploy TencentDB for Redis master and replica nodes in different AZs of the same region as instructed in Multi-AZ Deployment. Multi-AZ deployed instances have higher availability and better disaster recovery capability than single-AZ deployed instances.
Read/Write separation disabled (that is, replicas can be written to and read from): Write/read requests in a replica AZ are routed by proxy to the master node, and the master node synchronizes with replica nodes to ensure consistent data across all nodes. In this process, only one cross-AZ access happens.
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.
Note:
Currently, multi-AZ deployment is supported only for TencentDB for Redis 4.0, 5.0, and 6.2 standard architecture and cluster architecture.
2. Set parameters such as billing mode, region, instance edition, compatible version, architecture, and memory. For more information, see Creating TencentDB for Redis 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:
Deploy Redis nodes in different AZs. Up to six AZs are supported.
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.
flag in the AZ column are multi-AZ deployed. You can view their AZ information.
In the instance list, click the instance ID to enter the management page. On the Instance Details tab, instances with the
flag in the AZ section are multi-AZ deployed. You can view their AZ information.
In the instance list, click the instance ID to enter the management page. On the Node Management tab, you can view the details of nodes in different AZs.
Yes
No
Was this page helpful?