Design 47 H2: H-A-435 addendum, builder_health in the runner's form
This commit is contained in:
@@ -559,3 +559,8 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
|
||||
indexer's watch of `heard` (the bus's expiry marker); the re-pin revision is written at that expiry or at the first
|
||||
pipeline-started or step-ended of the pipeline, whichever comes first. A context deadline is a timer the test does not
|
||||
see and breaks the same rule. P-NATS-native.
|
||||
- **H-A-435 (addendum, 01:41)** A tools bundle cannot read a consumer's info, so builder_health takes the runner's form
|
||||
whole: the builder's events hub is wrapped in a process.ConsumerLedger that writes each consumer's facts at every
|
||||
delivery and every apply into a new builder state `consumers` (8 MiB), and the tool reads that state; "read when the
|
||||
health is asked" reads so (the bus is read at each event, no timer). The ledger's oldest-unacknowledged covers
|
||||
delivered messages only, as the runner's does. P3.
|
||||
|
||||
Reference in New Issue
Block a user