TiProxy keeps session migration when its network is unstable
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 73
- Forks
- 41
- Avg merge
- 21h 3m
- Merged PRs (30d)
- 21
Description
Development Task
If the network of TiProxy itself is unstable, the health check of all TiDB instances will also be unstable.
- It thinks tidb-0 is unavailable due to ping timeout, and migrates the sessions from tidb-0 to tidb-1
- After 10 seconds, it thinks tidb-0 is available again and thinks tidb-1 is unavailable, then it migrates sessions back
If TiProxy keeps migration, the performance will be degraded even worse.
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
Start by tracing TiProxy's health-check and session-migration paths, then reproduce the unstable-network scenario described in the issue. The work is done when transient health-check failures no longer cause repeated migrations and regression coverage verifies the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, databases, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100