tiup cluster scale-out operation is not idempotent
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?
tiup cluster scale-out xxx.yaml
Three tidb nodes failed to be added, but some TIDB nodes succeeded。
If you run the command again, an error message is displayed。
-
What did you expect to see?
tiup automatically ignores deployed nodes. -
What did you see instead?
Error: port conflict for '4005' between 'tidb_servers:172.17.0.7.port' and 'tidb_servers:172.17.0.7.port'
An error message indicating port conflict is generated
- What version of TiUP are you using (
tiup --version)?
1.13.0 tiup
Go Version: go1.21.0
Git Ref: v1.13.0
GitHash: 0ed23db6f45b03f752c9d675c2431454ac8f82a9
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 tiup cluster scale-out xxx.yaml with a partial failure, then retry the same command and inspect the scale-out entry point and cluster configuration handling. Done means already deployed TiDB nodes are ignored on retry instead of producing a duplicate port-conflict error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100