Waiting for tidb instances ready 127.0.0.1:4000 ... Error
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?
Start the cluster with tiup --tag test playground and exit. After the second login, 127.0.0.1:4000... Error
-
What did you expect to see?
127.0.0.1:4000... Done -
What did you see instead?
127.0.0.1:4000... Error -
What version of TiUP are you using (
tiup --version)?
1.11.3
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 tiup --tag test playground using TiUP 1.11.3, then repeat the second login and compare the reported status with the expected Done result. Trace the playground startup and readiness check entry points; done means the second login reaches 127.0.0.1:4000... Done without the 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
- 30/100