Fact 118
At both 50% and full production, repeated ingest-edge noisy-tenant tests preserved the eight-waiting-per-tenant cap, immediately inserted newly queued low-volume tenants into the ring, used every eligible slot through work-conserving dispatch, removed empty tenants from the ring after cancellation, and retained Retry-After on every queue-cap response.
Source evidence (1)
001621Jul 5, 2024 / 09:15 UTC-04:00
The mapped owner completed the remaining ingest-edge rollout. At 50% and full production, repeated noisy-tenant tests preserved the eight-waiting cap, newly queued low-volume tenants entered the ring immediately, and work-conserving dispatch used each eligible slot. Empty tenants disappeared from the ring after cancellation, every queue-cap response retained Retry-After, and the existing active-work, accepted-point, dropped-point, and restart checks remained clean. Update `rb_ingest_edge_cutover` with the production tenant-fair queue behavior while explicitly preserving the existing four-active-per-pod, two-active-per-tenant, bounded-decompression, and retry requirements.
Message 001621 in history