Linux host failure
Prepare for Linux host failures by shutting down a percentage of your hosts and observing the results. Validate that your infrastructure handles host loss without impacting service availability.
Experiment types
Shutdown
Targets
Linux
Length
20 minutes
How this Scenario works
This Scenario shuts down a percentage of your Linux hosts, simulating real-world hardware failures, power outages, or cloud instance terminations. It lets you observe whether your infrastructure can handle the loss of multiple hosts simultaneously.
Why run this Scenario?
- Validate that your load balancers detect failed Linux hosts and redistribute traffic to healthy ones.
- Test your infrastructure's capacity to absorb workload when hosts are lost.
- Verify that auto-recovery mechanisms (such as cloud auto-scaling groups) replace failed Linux instances.
- Build confidence in your migration to cloud-based infrastructure by understanding host failure behavior.
What to expect when you run it
When a percentage of Linux hosts are shut down, remaining hosts absorb the workload and services continue running without interruption.
More Scenarios to try
Kubernetes packet loss
Ensure your Kubernetes systems can detect and route around resources that fail health checks. This Scenario gradually increases packet loss to validate liveness/readiness probe and load balancer behavior.
Container packet loss
Ensure your containerized systems can detect and route around resources that fail health checks. This Scenario gradually increases packet loss to validate health check and load balancer behavior.
Windows packet loss
Ensure your Windows systems can detect and route around resources that fail health checks. This Scenario gradually increases packet loss to validate health check and load balancer behavior.
Avoid downtime. Use Gremlin to turn failure into resilience.
Gremlin empowers you to proactively root out failure before it causes downtime. See how you can harness chaos to build resilient systems by requesting a demo of Gremlin.
.svg)