tiup playground cannot be restarted, when the default ports are occupied
Open
Nobody has claimed this yet.
status/TODO
type/bug
- 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?
- default ports(2379/4000/20160 etc) are occupied
tiup -T test playground nightly --host=xxx.xxx.xxx.xxx --db=1 --pd=1 --kv=1 --tiflash=0 --monitor- do something in TiDB
- ctrl-c to exit playground
tiup -T test playground nightly --host=xxx.xxx.xxx.xxx --db=1 --pd=1 --kv=1 --tiflash=0 --monitor
- What did you expect to see?
- The cluster is restarted.
- What did you see instead?
- The cluster cannot start because a random port different from the first start is assigned.
- What version of TiUP are you using (
tiup --version)?
❯ tiup --version
tiup version v1.0.3 tiup
Go Version: go1.13
Git Branch: v1.0
GitHash: 5accd57
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 issue with the listed tiup playground command while ports 2379, 4000, and 20160 are occupied, then repeat it after Ctrl-C. Trace the playground startup and port-assignment entry points. Done means the cluster restarts successfully with the expected port behavior on the second launch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100