Fact 110
Alex Valdez requests that the existing `rb_ingest_edge_cutover` playbook be updated to state that randomized one-to-three-second `Retry-After` behavior is now the production behavior, document the explicit stop boundaries, and record the observed maxima from the 10%, 50%, and 100% gates.
Source evidence (1)
001286Apr 2, 2024 / 12:46 UTC-04:00
The full-production observation is complete. Peak retries are 129,000 attempts per second, p99 peaks at 188 ms, queue depth peaks at 75%, accepted throughput remains 2.9% below baseline, and no 5xx increase appears. All production gates passed, so ingest-edge v2.19.4 remains at 100% rather than returning to the baseline behavior. Update the existing cutover playbook `rb_ingest_edge_cutover` to state that randomized one-to-three-second `Retry-After` behavior is now the production behavior, record the explicit stop boundaries, and record the observed maxima from the 10%, 50%, and 100% gates. The formal 48-hour production check is still due April 4.
Message 001286 in history