robustmq-chaos-test

Simulate broker-kill and network-delay faults to validate RobustMQ SDK clients.

1.8k|249|Updated Aug 3, 2023
One-click install
npx skills add https://github.com/robustmq/robustmq --skill robustmq-chaos-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: robustmq-chaos-test
Source: https://github.com/robustmq/robustmq/tree/main/chaos-test
Command: npx skills add https://github.com/robustmq/robustmq --skill robustmq-chaos-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires cluster_manage, observability, client, chaos, report, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides automated chaos testing for RobustMQ, simulating faults like broker failures and network delays to ensure client resilience.

Core Features & Use Cases

  • Automated Chaos Testing: Simulates faults like broker kill and network delay to test client resilience.
  • Multi-language Support: Validates SDK clients in Python, Go, Rust, and Java.
  • Reporting: Generates a Markdown + JSON report on GitHub with results.
  • Use Case: Ensure your RobustMQ SDK clients can handle unexpected failures and recover gracefully, even under adverse network conditions.

Quick Start

Run the chaos test using the command: run a chaos test round

Frequently Asked Questions about robustmq-chaos-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run chaos testing for message broker failures and network delays?

Chaos testing for message broker failures validates SDK client resilience by simulating broker kill and network delay faults. This Skill automates fault injection to ensure clients handle unexpected failures and recover gracefully under adverse network conditions.

Can I test SDK client resilience across multiple programming languages?

Yes, you can test SDK client resilience across Python, Go, Rust, and Java. The chaos simulation validates multi-language SDK client responses against injected broker failures and network delays.

What tools do I need to simulate broker failures and network partitioning?

Simulating broker failures and network delays requires tools for cluster management, observability, clients, chaos injection, and reporting. These components coordinate to inject faults, monitor system behavior, and validate SDK client responses.

How are chaos test results reported and published?

Chaos test results are reported by generating a Markdown and JSON report published on GitHub. This provides a structured summary of client resilience against simulated broker failures and network delays.

Can I schedule automated resilience testing on a cron schedule?

You can schedule automated resilience testing using cron. The Skill utilizes cron for scheduled testing, allowing regular simulation of broker kill and network delay faults to continuously validate SDK client resilience.