mirror of
https://github.com/XRPLF/rippled.git
synced 2026-08-21 06:10:58 +00:00
b82ee49cca
The runbook told operators to read a missing outcome as "never went to the network", which stopped being true once the abort path started setting it, and the glossary still described outcome as a two-value split. Document all three values, where each is written, and why peer_count is absent on the abort path. Several claims were wrong and are corrected: - Give-up is reached at about 18s, not 21s. There is no setTimer call, so the first timer runs immediately and the old derivation counted a wait that does not happen. - A live aborted rate does not imply stalled acquisitions. A clean shutdown clears every in-flight acquire, the admin fetch_info clear does the same, and a full job lane stops timeouts advancing so give-up cannot fire. The runbook already said the last of these elsewhere. - A missing outcome does not mean exactly one thing. tryDB can set failed_ and return before done() runs, exporting a span with no outcome at all. - failed covers unusable ledger data as well as exhausting the retry limit, so a failed span can carry timeouts=0. - The aborted lower bound of one minute holds only on the sweep path. - The sweep measures time since anything last asked for the ledger, not since data last arrived. Also fixes the mainnet verification command, which still used the old RPC port, and drops an inaccurate claim from the config comment about which ports the workload scripts use.