tencent cloud

Feedback

Experiments on CVM Intra-host Network Latency

Last updated: 2024-09-26 15:47:38

    Background

    Network latency fault is one of the common issues. When such a fault occurs, it will result in the service not responding to user requests properly, and impact the normal operation of businesses will be affected. For businesses that rely on high availability and low delay, network latency will cause great inconvenience and loss to users.
    To improve network reliability and stability in CVM, network delay fault experiments are required. Through the experiments, the capability of the system for normal operation in the situation of network delay can be verified and issues in this fault scene can be revealed in advance so that system architecture can be optimized and contingency plans can be prepared.

    Experiment Implementation

    Step 1: Experiment Preparation

    Prepare several CVM instances that are available for the experiment.

    Step 2: Experiment Orchestration

    1. Check network status before fault injection. Send messages to the target machine through ping commands and wait for a response from the target machine. Check network latency.
    
    
    2. Log in to the Tencent Smart Advisor > Chaotic Fault Generator, go to the Experiment Management page, and click Create a New Experiment.
    3. Click Skip and create a blank experiment. Fill in the experiment information, and select a CVM instance for the experiment objective.
    4. Click Add Now, select Network Resources, click Intra-host network latency, and click Next.
    5. Configure fault action parameters, and click Confirm.
    6. After action parameter configuration, click Next. Configure Guardrail Policy and Monitoring Metrics considering actual situations, and click Submit to complete experiment creation.

    Step 3: Experiment Execution

    1. Go to experiment details, and click Go to the action group for execution.
    2. Click Execute to start an experiment.
    3. Click the Action Card to check the details for the action execution results.
    4. Check host network status after fault injection. It can be found that when the target machine is pinged again, the returned network packet has been delayed.
    
    
    5. Execute a recovery action, and check details of the recovery action.
    6. Check recovery result. When the target machine is pinged again, it can be seen that the fault has been cleared and normal network speed has recovered.
    
    
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support