jschoubben
b1546ed28a
mesh/delivery-group group feat/335-a-busy-container-is-replaced-when-idle rejected: its order contradicts itself: novox/mesh-catalog@190608193764, novox/mesh-c…
mesh/merge-gate out of date: judged against trunk 56d6313262e8, the trunk is now cbac703e817d; judged again on a recheck or when it is merged
mesh/repo-check out of date: judged against trunk 56d6313262e8, the trunk is now cbac703e817d; judged again on a recheck or when it is merged
mesh/delivery superseded: a newer head of the same pull request
A merge into mesh-controller replaced every build agent and threw away the checks in flight (issue 594). The manifest's container busy is checked and sent only to an engine that reads it; a report's busy waits are kept, the gate starts at the report that says the container replaced, and the wait is a phase of the delivery time. mesh-builder busy drains the agent and answers while a build is in hand (novox/hq ADR 0335).
12 lines
932 B
SQL
12 lines
932 B
SQL
-- A machine's report says which container it left running because it said busy, and which it replaced
|
|
-- after it waited (novox/hq ADR 0335, issue 594).
|
|
--
|
|
-- A send that replaced the build agent killed the check it ran, and the queue started it again elsewhere.
|
|
-- A container may now declare `busy`; the node-engine asks it before replacing it, leaves it running while it
|
|
-- says busy, within 15 minutes, and says so in its report's `busy`: [{"id", "container", "state", "since",
|
|
-- "until", "said"}], state `waiting`, `replaced-when-idle` or `replaced-at-bound`. Kept with the machine's
|
|
-- last account, so a walk's first-machine gate waits while its module's container is listed waiting — across
|
|
-- a restart of the controller, which a merge into mesh-controller makes in the same walk that moves the build
|
|
-- agent. Empty from an engine that never waits.
|
|
alter table node_report add column busy jsonb not null default '[]';
|