Primary-secondary Nodes in TencentDB for Redis Instance Unavailable
Last updated: 2024-09-26 15:47:38
Background
TencentDB for Redis supports multi-availability zone deployment. Users can deploy their businesses in multiple availability zones to improve the high availability of systems. Users can use primary-secondary nodes unavailability fault in TencentDB for Redis provided by Tencent Smart Advisor-Chaotic Fault Generator to simulate such scenes so that disaster recovery and overall high availability of their business systems can be verified.
Experiment Implementation
Step 1: Experiment Preparation
A TencentDB for Redis Instance
A CVM instance connected to Redis instance network (used for logging in a CRS instance).
Note:For creating and logging in a CloudDB instance, see the following documents:
2. Click Skip and create a blank experiment, fill in experiment information, select TencentDB for Redis Memory Edition under Cloud Resource Type for Experiment Resource Object, and add an instance.
3. Click Add Now to add an experiment action, select Primary-secondary node unavailable and then click Next.
4. Configure action parameter information for fault actions and click Confirm.
5. After action parameter configuration, click Next. Selectively configure Guardrail Policy and Monitoring Metrics considering actual situations. After checking and confirming all configurations, click Submit to complete the experiment creation.
Step 3: Experiment Execution
1. Try to log in to a TencentDB for Redis instance through CVM.
2. Go to Experiment Details. In the Experiment Action Group, click Execute to start executing an experiment.
3. After fault injection, log in to a TencentDB for Redis instance through CVM once again.
4. Execute a recovery action and log in to TencentDB for Redis through CVM once again. Redis connection is recovered.
Yes
No
Was this page helpful?