Release Notes
Announcements
Inspect Node Information
Scenarios
Tencent Cloud Distributed Cache supports viewing and managing node information of instances, helping Ops personnel efficiently manage instance nodes and quickly locate related abnormalities during node operation.
Node information view: Supported viewing information such as node ID, role, running status, and usage capacity.
Node management operations: supports adjusting node specifications, promoting replica nodes to primary nodes, enabling replica read-only, primary/secondary failover, and other operations.
Version Description
Storage Engine | Supported Versions | Supported Architectures |
Redis Edition | 4.0 and above | Standard Architecture, Cluster Architecture |
Valkey Edition | 8.0 | Standard Architecture, Cluster Architecture |
Memcached Edition | Not supported | |
Viewing Node Information
1. Log in to the Tencent Cloud Distributed Cache console.
2. At the upper part of the Instance List page on the right, select a region.
3. Locate the target instance for which you need to view nodes in the instance list.
4. Click its Instance ID to go to the Instance Details page, and click the Node Management tab.
Standard architecture
Parameter Name | Parameter Description |
Node ID | The node ID number of the database instance. |
Role | The role of the current node, either a primary node or a replica node. |
AZ | The AZ to which the current node belongs. |
Monitoring | Click  |
Status | The running status of the current node. |
Slots | The value range of slots on the node. |
Used Memory | The memory usage of the node. |
Cluster structure
Single AZ
Multiple AZs
Parameter Name | Parameter Description |
Shard Name | Database sharded cluster shard name. The shard name is formed by concatenating `Instance ID_shard_Shard Number`, where the shard number starts from 1 and is arranged in natural number sequence. For example: crs-mufy****_shard_1. |
Node ID | The node ID number of the database instance, automatically and randomly generated by the system as the unique identifier of the node. |
Node Group Name | For a multi-AZ instance deployed in cluster architecture, this parameter is displayed. Primary nodes with multiple shards are logically grouped as a primary node group, and replica nodes are logically grouped as a secondary node group (replica group). The name of each node group is formed by concatenating 'ng-' with a number, where the number starts from 00 and is arranged in natural number sequence. The name of each node group indicates the primary or replica role of the node. |
Role | For single-AZ instances deployed in cluster architecture, this parameter is displayed to indicate the primary or replica role of the node. |
AZ | The AZ to which the node belongs. For a multi-AZ instance, whether it is a primary AZ or secondary AZ is indicated. |
Monitoring | Click  |
Status | The running status of the current node. |
Slots | The value range of slots on the node. |
Used Memory | The memory usage of the node. |
More Operations
Configuration changes
On the node management page, you can adjust the configuration specifications of the instance, including: scaling up/down node memory capacity, adding/deleting replicas, adding/deleting shards (cluster architecture), and other operations. The operation entry is shown in the figure below. Go to the configuration change window. For specific configuration details, see Change Instance Specifications.
Replica promotion to primary
For instances deployed in a single AZ, Tencent Cloud Distributed Cache supports manually promoting replica nodes to master nodes. For multi-AZ instances, Tencent Cloud Distributed Cache supports promoting replica nodes to master nodes. For cluster architecture, it supports promoting replica node groups to master node groups and elevating the AZ where the source replica node or replica node group resides to the primary AZ. For specific operations, see Manually Promoting Master Nodes.
Fault Simulation
To facilitate failure simulation testing for business operations, the Tencent Cloud Distributed Cache provides a failure simulation feature for instances deployed in multi-AZ deployment. You can use this feature on the node management page in the console. For specific operations, see Failure Switchover.
Read-Only Replica
On the Node Management page, when the database instance has one or more replicas, you can enable automatic read-write separation to scale up read performance. For more details, see Enabling and Disabling Read-only Replicas.
Related APIs
API | API Description |
Queries instance node information. | |
Queries node detailed information. |
피드백