diff --git a/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md b/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md index 2cb89581..f46d62c0 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md +++ b/03-DESIGN/01-to-be/47-milestones/H-deliver-the-delivery-system.md @@ -668,3 +668,4 @@ Added by the lead at 21:30 CET, from the run of 19:50 to 21:30; a row met again | The builder's events backlog (row 148) drained at only fifty a minute under the new builder, holding up every publish and so every pipeline waiting on one: a published at a version many reservations share still cost three seconds (the fallback by version read every reservation at the version, and the journal line read them all again), and the SDK's event hub pulls five hundred messages per pull and handles them one by one, so buffered messages outlive the thirty-second ack wait and are given again (almost every outstanding message redelivered) and handled twice. Every recovery loses something (a purge of the consumer would drop take-ins, source moves and conditions among the publisheds), so the backlog drains while the fixes build (rows 144 and 148); the builder and mesh-sdk. Settled by H-A-280 (each reservation read once, the fallback only over the unbuilt ones, in-progress sent before long work) in the builder and H-A-281 (the hub pulls at most twenty per pull and keeps a slow handler alive with in-progress) in the SDK for every module, both in build. | H1 | | Row 149's two fixes: the builder's (each reservation read once, the fallback over the unbuilt only, in-progress before the slow pass) was approved and merged at 16:47 as a pipeline of eight movers, its pack for the build node following; the SDK's (the event hub pulls at most twenty messages per pull and sends in-progress every third of the ack wait for a handler still running) is built and in review, and reaches every module at its next build against the new SDK release (row 149); the builder and mesh-sdk. | H1 | | The SDK's event hub fix (row 150) merged at 16:51, and its release re-pins 126 modules into one pipeline, the tool runner among them. Every merge of the afternoon moved the tool runner to a newer pipeline before the older one could pass (rows 142 and 147), so the lead holds further merges from 16:52 until the queue runs through to the tool runner's pass; the one approved change still unmerged (row 146) waits on the operator's word. The builder's read-once pack goes onto the build node meanwhile, so the events backlog drains faster (rows 142, 146 and 150); the pipeline runner (`mesh-delivery-pipeline`), the builder and the runbook. | H1 | +| The builder was built again against the SDK's hub fix (row 151) and placed on the build node at 16:58 (its read-once pack at 16:52 before it, with no change in the drain rate): the redelivery stopped (two redelivered, against 175 before; nineteen unacknowledged, against the batch of twenty), and the drain rose to about 1.2 messages a second, so the backlog of 2,167 at 17:05 falls under the bound in about half an hour. What remains is about one second of work per event. Each restart of the builder cut one publish in flight, which the loop asking a publish again asked again; the tool runner's release 0.1.40 waits in main.117 on thirteen publishes (rows 149, 150 and 151); the builder. Owed: the cost per event of the builder's published handling, measured and cut. | H1 (the fixes live); H2 (the cost per event) |