Details
-
New Feature
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.7.0
-
None
-
None
Description
To test failure resilience today you either need custom scripts or implement Chaos Monkey-like logic in your application (SLIDER-202).
Killing AMs and containers on a schedule & probability is the core activity here, one that could be handled by a CLI App/client lib that does this.
- entry point to have a startup delay before acting
- frequency of chaos wakeup/polling
- probability to AM failure generation (0-100)
- probability of non-AM container kill
- future: other operations