Simultaneous WebSocket disconnects cause synchronized retry waves
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Simultaneous WebSocket disconnects cause synchronized retry waves
- Load ten active tasks connected to the same service endpoint.
- Interrupt the transport once for all connections.
- Record retry timestamps per task.
Expected: exponential backoff includes per-connection jitter and a shared connectivity signal coalesces retries after a common outage.
Actual: retries cluster at the same timestamps across tasks, amplifying a single disconnect into a retry wave. A 24-hour sample contained 122 retries concentrated around shared disconnects. Suggested fix: full jitter, one connectivity probe per endpoint/account, and idempotent resume tokens so recovery cannot duplicate output.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the WebSocket reconnect and exponential-backoff entry points, then reproduce the ten-connection disconnect scenario and record retry timestamps. Done means retries are desynchronized with per-connection jitter, shared recovery is coalesced per endpoint or account, and resume behavior does not duplicate output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100