Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Playground incorrectly detected that tidb failed to start #962

Closed
unbyte opened this issue Dec 2, 2020 · 1 comment · Fixed by #968
Closed

Playground incorrectly detected that tidb failed to start #962

unbyte opened this issue Dec 2, 2020 · 1 comment · Fixed by #968
Labels
type/bug Categorizes issue as related to a bug.

Comments

@unbyte
Copy link
Contributor

unbyte commented Dec 2, 2020

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?
tiup playground --host 0.0.0.0 --tiflash 1
  1. What did you expect to see?

outputs

To connect TiDB: mysql --host %s --port %s -u root

and start tiflash

  1. What did you see instead?

tidb start successfully but outputs

Playground Bootstrapping...
Start pd instance
Start tikv instance
Start tidb instance
Waiting for tidb localhost:4000 ready  ... Error
To view the dashboard: http://localhost:2379/dashboard
To view the Prometheus: http://0.0.0.0:9090
To view the Grafana: http://0.0.0.0:3000
  1. What version of TiUP are you using (tiup --version)?
v1.2.0 tiup
Go Version: go1.13
Git Branch: bump
GitHash: 7e35be8

I use tiup in Ubuntu 18 for WSL. And this happens occasionally.

@unbyte unbyte added the type/bug Categorizes issue as related to a bug. label Dec 2, 2020
@unbyte
Copy link
Contributor Author

unbyte commented Dec 2, 2020

It's due to that in my host tidb can't be connected until after 60 attempts to connect. can provide any way to set a custom max wait time for starting tidb?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Categorizes issue as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant