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

ebs br: avoid to allocate warmup pods to the same node #5200

Closed
BornChanger opened this issue Jul 25, 2023 · 0 comments · Fixed by #5229
Closed

ebs br: avoid to allocate warmup pods to the same node #5200

BornChanger opened this issue Jul 25, 2023 · 0 comments · Fixed by #5229
Assignees
@WangLe1321
Labels
area/ebs-br severity/minor type/bug Something isn't working

Comments

@BornChanger
Copy link
Contributor

Bug Report

What version of Kubernetes are you using?

What version of TiDB Operator are you using?

What storage classes exist in the Kubernetes cluster and what are used for PD/TiKV pods?

What's the status of the TiDB cluster pods?

What did you do?

Run EBS br with warmup

What did you expect to see?

Warmup can run with high efficiency

What did you see instead?

Warmup goes very slowly and it turns out multiple warmup pods are allocated to the same node.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@WangLe1321 WangLe1321

Labels
area/ebs-br severity/minor type/bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

br: add warmup process to volume snapshot restore WangLe1321/tidb-operator
2 participants
@WangLe1321 @BornChanger