pub const MAX_CONCURRENT_AUDIT_RESPONSES: usize = 8;Expand description
Maximum number of concurrent in-flight audit-responder tasks.
Subtree (round 1) and byte (round 2) challenge handlers are spawned off the
serial replication message loop so their disk reads don’t stall replication.
This caps how many run at once across the engine, restoring backpressure: a
peer flooding audit challenges cannot fan out unbounded get_raw reads or
multi-MiB byte serves. When the cap is hit, the challenge is dropped — the
auditor graces a non-response as a timeout, so honest auditors are
unaffected and only a flooder is throttled. Sized to cover a handful of
concurrent honest auditors (the per-peer gossip-audit cooldown is 30 min, so
genuine concurrent audits are few) while bounding the byte round’s worst-case
resident bytes (N × MAX_BYTE_CHALLENGE_KEYS × MAX_CHUNK_SIZE).