Design 47 H: H-A-280 and H-A-281, a published read once; the event hub pulls small batches and keeps slow handlers alive

This commit is contained in:
2026-11-21 16:42:14 +01:00
parent f34301e08d
commit 20fbb3acbc
@@ -1607,3 +1607,14 @@ Where two preparers disagreed, the chosen one is named.
registry holds at another digest is built again at the next free number (the reserve skips held numbers, H-A-275,
and records fresh digests); no move keeps digests; the finding version-held-elsewhere names both digests and
clears at version-released. P2 (the published bytes carry the number they are published under), P4.
- **H-A-280 (a published event reads each reservation once, and only the unbuilt ones on a miss, 16:42)** Amends
H-A-271: the builder's published handling reads the reservations at a version once and hands them on to its
marking and its journal line (no second read); the fallback by version reads only reservations not yet built
(the index by version keeps them apart from the built); the handler says in progress to the bus before work that
may outlast a third of the ack wait. Met live: a published at a version fourteen reservations share cost three
seconds, read twice, and the backlog drained at fifty a minute. In the builder. P7, P4.
- **H-A-281 (the SDK's event hub pulls small batches and keeps slow handlers alive, 16:42)** Met live: the 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 (every outstanding message redelivered), handled twice. The hub pulls at most twenty messages
per pull and sends in-progress for a handler that runs past a third of the consumer's ack wait, so no buffered
message is redelivered for waiting in the client. In the SDK (the event hub), for every module. P4, P7.