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.

Sign up for GitHub

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

Jump to bottom

one tidb cluster's scheduling issues block other clusters #683

Closed
gregwebs opened this issue Jul 23, 2019 · 1 comment
Closed

one tidb cluster's scheduling issues block other clusters #683

gregwebs opened this issue Jul 23, 2019 · 1 comment
Assignees
@weekface
Labels
test/stability stability tests type/bug Something isn't working

Comments

@gregwebs
Copy link
Contributor

Bug Report

See this discussed in #468. I retested with operator rc1. When one TiDB cluster has a scheduling failure, then a second one cannot be started.
The custom scheduler never considers the second cluster.
@gregwebs gregwebs added type/bug Something isn't working test/stability stability tests labels Jul 23, 2019
@gregwebs
Copy link
Contributor Author

I cannot reproduce this anymore

yahonda pushed a commit that referenced this issue Dec 27, 2021
@cofyc @ti-srebot
zh: improvements from Queeny Test (#683)
1e6be0d 
Co-authored-by: ti-srebot <66930949+ti-srebot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@weekface weekface

Labels
test/stability stability tests type/bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gregwebs @weekface