tencent cloud

Tencent Smart Advisor-Chaotic Fault Generator

Product Introduction
Overview
Strengths
Scenarios
Purchase Guide
Purchase Instructions
Getting Started
Quick Start with the Console
Quick Start with API
Operation Guide
Template Library
Experiments
Fault Action
Guardrail Monitoring
Tag
Agent Management
Fault Action Library
Compute
Database
Network
Container
Big Data
Cloud Load Balancer
Message Queue
Direct Connect
Custom Actions
Cloud Streaming Services (CSS)
Permission Management Guide
Overview
Authorization Policy Syntax
Authorizable Resource Types
Service Authorization and Role Permissions
Sub-users and Authorization
API Documentation
History
Introduction
API Category
Making API Requests
Task APIs
Template Library APIs
Data Types
Error Codes
FAQs
Product Feature Issues
Action Execution Issues
Agent FAQ
Related Protocol
PRIVACY POLICY MODULE CHAOTIC FAULT GENERATOR
DATA PRIVACY AND SECURITY AGREEMENT MODULE CHAOTIC FAULT GENERATOR
Contact Us

Action Execution Issues

PDF
Focus Mode
Font Size
Last updated: 2024-09-26 15:34:19

How to Handle the Abnormal Instance Lock Mechanism?

Action execution failed, prompting that the current instance is being injected with faults by other actions
To prevent the inaccurate observation of instance behavior after injecting the same type of fault into the same instance, the platform has implemented an instance lock mechanism. This ensures that only a single fault action can be executed on the same instance at any given time, with other actions being excluded. However, the platform also considers that some actions do not interfere with each other and do not need to compete for the same instance lock. Therefore, the platform distinguishes lock types based on the action type. For example, CPU-related fault actions and memory-related fault actions are allowed to execute simultaneously, but actions of the same type cannot be executed at the same time.

What Are Common Issues with CVM?

Network failure action execution failed, prompting the message Error: Exclusivity flag on, cannot modify.
The TC rules issued for this fault conflict with the existing rules, making it impossible to overwrite the current rules. You can check if there are any previous experiment actions that were not properly recovered, or modify the configuration parameters to forcefully overwrite the existing rules.
Failed to execute IO Hang action, prompting that the operating system acquisition failed
The user's operating system does not support the execution of this action. Currently, the platform supports the following system versions: CentOS 7.2 and later, Debian 8.2 and later, Ubuntu 16.0.4 and later, and TencentOS.

What Are Common Issues with Redis?

Failed to execute primary-secondary switchover action, prompting that the instance does not exist cross AZ replicas and primary-secondary switchover cannot be executed
The instance is upgraded to support cross-availability zone deployment, but no cross-availability zone nodes are present, so Redis cannot perform the primary-secondary switch. You need to go to the Redis instance details and add replicas in other availability zones before you can simulate the primary-secondary switch.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback