Design 47 H: H-A-296, no responders is a wait, not an end
This commit is contained in:
@@ -1715,3 +1715,9 @@ Where two preparers disagreed, the chosen one is named.
|
||||
(the fault was the bed's, not the program's). A teller fault met on the way, two takers of registration-changed
|
||||
since the SDK's views reader also takes its bare subject, is fixed in the same branch as its own commit (A-199,
|
||||
A-222). P3, P7.
|
||||
- **H-A-296 (no responders is a wait, not an end, 19:27)** Met live: the tool runner's pipeline ended failed at 19:21:50
|
||||
because its composition step's compose-candidate asks met "no responders" on three node-engines at once (every
|
||||
engine answered discovery three minutes later); the lead reran the step. A seat ask that meets no responders is not
|
||||
a verdict: the asker (the holder of mesh-wants for compose-candidate, the runner for its step asks) asks again with
|
||||
a short back-off until the ask-unanswered bound (H-A-243) and ends could-not-run only then, naming every try. Owed,
|
||||
H2: in the assigner's composition run and the runner's asks. P-NATS-native (a holder may be between two lives), P3.
|
||||
|
||||
Reference in New Issue
Block a user