Tiup lack the port conflict detection of the tiflash
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
- What did you do?
deploy the tiflash with the flash_proxy_status_port and metrics_port having the same port
-
What did you expect to see?
failed -
What did you see instead?
successfully deploy and start the cluster.(The tiflash also lack the port conflict detection).
This results in proxy port being covered by metrics port, and the process of replication is unavailable. -
What version of TiUP are you using (
tiup --version)?
1.4.0 tiup
Go Version: go1.16.2
Git Ref: v1.4.0
GitHash: eb335e6ad9d0dc19d1c43db422cd409d62bc3cea
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 a TiUP deployment with flash_proxy_status_port and metrics_port set to the same value, using the reported TiUP 1.4.0 setup. Trace the deployment validation path and confirm that the deployment fails before the cluster starts when the ports conflict.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100