Code RoomLong-running matches evicted during rollout
HardPrep Room Coding #2817

Long-running matches evicted during rollout

On-callReliability & on-callSenior–Staff~40 min

A rolling deploy updates the authoritative game-server binary that hosts live match sessions (sticky: a match lives on one server for its duration). The deploy drains and replaces servers as matches end — but to roll quickly, the orchestrator also evicts servers whose matches are merely 'long-running.' Mid-rollout, players in long matches (ranked games >30 min) get disconnected mid-game in a wave, ranked results are voided, and the matchmaking queue spikes as those players re-queue. Dashboards: per-server, match-count drains to zero normally on most, but a cohort of servers hosting long matches were force-evicted at their drain deadline; disconnect events cluster on those evictions; CPU/error rate otherwise normal. Triage, explain, and prevent.

What a strong answer looks like

Stop the bleeding first (mitigate), then form hypotheses from real signals. Separate root cause from symptom, communicate status as you go, and close with what prevents a repeat.

0:00 of about 40 min
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.