b6f42c667a
_drain_control_watcher polls drain_requested() once a second, and that does a synchronous Path.read_text() on the marker file. At a 1s cadence that is ~86k blocking disk reads a day sitting on the event loop. It stays invisible until the host is under I/O pressure, at which point a single read can stall for 30s+ and take every platform heartbeat down with it. Observed as repeated "discord.gateway: Shard ID None heartbeat blocked for more than 30 seconds" followed by the Discord websocket dropping, with the gateway still reporting active. Move the call to asyncio.to_thread so the read blocks a worker thread instead of the loop. Semantics are unchanged: drain_control never raises, the surrounding try/except still covers it, and the sequential await means at most one probe is in flight at a time.