auto-update: a rebuild is live until its whole subtree is terminal
rebuild_live checked only MetaSync, which finishes in 0.2 s, so the next 5-min pass queued a second rebuild while the first still held the stop, swap and start. It now covers MetaSync, AgentWindow, Prebuild, StopForUpdate, Swap and RebuildBookkeeping. AgentWindow is also the brace of a pause window, so an open pause skips that agent's pass too; the docs say so and a test pins it.
This commit is contained in:
parent
36515c289d
commit
12e797e7e3
1 changed files with 66 additions and 7 deletions
|
|
@ -312,9 +312,11 @@ store path the agent's `agent-closures` record declares) and persisted
|
|||
|
||||
Booting with every agent on its declared closure performs no rebuild — only
|
||||
reconciles. After the boot pass, `auto_update::run` repeats the rebuild half
|
||||
every five minutes. It skips an agent with a rebuild waiting or running
|
||||
(`JobQueue::rebuild_live`) and one whose declared store path this process
|
||||
already attempted, so a closure that fails to deploy gets one try per process.
|
||||
every five minutes. It skips an agent with a rebuild or a pause window waiting or
|
||||
running (`JobQueue::rebuild_live`: any node from `MetaSync` to
|
||||
`RebuildBookkeeping`, or an `AgentWindow`, still live) and one whose declared store path this
|
||||
process already attempted, so a closure that fails to deploy gets one try per
|
||||
process.
|
||||
|
||||
The boot log line records the rebuild / deferred / up-to-date counts so the
|
||||
operator sees at a glance how much work the boot triggered. `auto_update::run`
|
||||
|
|
|
|||
Loading…
Reference in a new issue