1s failover time when the TiProxy VIP owner shuts down
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 73
- Forks
- 41
- Avg merge
- 21h 3m
- Merged PRs (30d)
- 21
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
- Start a cluster with 2 TiProxy. TiProxy is configured with VIP.
- Clients connect to the VIP.
- Kill the TiProxy VIP owner.
- Check the failover time from clients.
2. What did you expect to see? (Required)
RTO=0
3. What did you see instead (Required)
RTO=1s
The log shows that when the old owner is down, the client connects to the new owner, but reports invalid connection. I'm afraid even if the new owner has bound the VIP, it still rejects connections with this VIP.
4. What is your version? (Required)
main
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 reproducing the two-TiProxy VIP setup described in the issue: connect clients, stop the VIP owner, and inspect the client-side invalid connection report. Trace the failover path and verify that connections through the new owner no longer encounter the reported one-second interruption.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100