Skip to main content

Module deadline

Module deadline 

Source
Expand description

The deadline checker: every fault ran, was cleaned up, and was recovered from in time; every path stayed inside its budgets.

A fault the schedule named but the evidence does not record fails, as does a recovery the fault kind implies but nobody measured. The alternative – judging only what was recorded – passes a run whose fault injector silently did nothing, which is the failure a soak is least able to notice by itself.

Structs§

BudgetVerdict
One latency percentile or throughput floor against its budget.
DeadlineVerdict
One recovery against its deadline.
FaultProblem
A scheduled fault the evidence shows was not executed cleanly.

Enums§

DeadlineOutcome
How one measured recovery compared with its deadline.

Constants§

START_SLACK
How late a fault may start against its scheduled offset. The executor resolves the target and the cluster state first, so it never starts early, but it may start a few seconds late.

Functions§

check_budgets
Check every path’s steady-window latency and throughput against its budget.
check_recoveries
Check every scheduled fault’s execution and recoveries.
checks_for
The recoveries fault is judged on when it landed on a broker with role.
deadline_for
The deadline check is judged against after fault.