Make documentation standalone and generalize examples
This commit is contained in:
@@ -6,11 +6,8 @@ listens any more. The supervisor restarts those tasks with a growing delay and
|
||||
stands a flow down when one keeps failing, because a flow crash-looping every
|
||||
second is worse than a flow that is visibly stopped.
|
||||
|
||||
Standing down is a rest, not a verdict. It used to be the end of the task: the
|
||||
flow stayed dead until somebody published it or the engine restarted. On a
|
||||
house that runs unattended that turns a broker rebooting at four in the morning
|
||||
into a hole in the record until someone notices — so the rest expires, the
|
||||
budget comes back, and the task tries again on a much longer clock.
|
||||
Quarantined tasks retry after a longer cooldown with a fresh restart budget.
|
||||
This lets unattended flows recover from extended connection failures.
|
||||
|
||||
Deliberately a plain task registry rather than a `TaskGroup`: a group cancels
|
||||
its siblings when one member fails, which is the opposite of what supervision
|
||||
@@ -38,8 +35,7 @@ BACKOFF = settings.FLOW_RESTART_BACKOFF
|
||||
# Per task rather than per flow: a flow whose subscriber and its keepalive
|
||||
# publisher both go down with the same broker spends one shared budget twice as
|
||||
# fast as it was sized for, and gives up before the backoff above has reached
|
||||
# its longest step. That is what took the house's inverter readings out for
|
||||
# nearly five hours — six crashes across two tasks inside 41 seconds.
|
||||
# its longest step.
|
||||
FAILURE_BUDGET = 5
|
||||
FAILURE_WINDOW = 300.0
|
||||
# How long a task sits out before its budget is handed back. Minutes rather
|
||||
|
||||
Reference in New Issue
Block a user