You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Failure Daemon will be configured to execute the following pattern for 1 hours every other hour (i.e., one hour active and 1 hour idle).
Hashtag Actor Service’s container crash every 5 minutes.
Hashtag Counter’s container crash every 4 minutes.
Hashtag Counter’s POD crash every 9 minutes.
Hashtag Snapshot Service crash every 7 minutes.
State store slowness for 1 minute every 29 minutes (tps to be defined during implementation).
Topic outage every 21 minutes.
Topic slowness for 1 minute every 23 minutes.
Dapr’s sidecar injector crash with Hashtag Snapshot Service every 13 minutes.
Dapr’s placement service crash with every 5 minutes.
Actor’s instantiation burst for 1 minute every 10 minutes (tps to be defined during implementation).
In case all the failures above do not prove practical together in real world, the Failure Daemon can randomly choose a subset of the failure configurations above (5, for example) and execute only those in a given run.
The text was updated successfully, but these errors were encountered:
msfussell
changed the title
[Longhaul Chaos Test] Failure Daemon Configuration - Part 2
[Chaos Test] Failure Daemon Configuration - Part 2
Mar 24, 2020
The Failure Daemon will be configured to execute the following pattern for 1 hours every other hour (i.e., one hour active and 1 hour idle).
In case all the failures above do not prove practical together in real world, the Failure Daemon can randomly choose a subset of the failure configurations above (5, for example) and execute only those in a given run.
Parents: #11 #22
The text was updated successfully, but these errors were encountered: