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: restore data should be after tikv nodes are all ready #5242

Closed
BornChanger opened this issue Aug 14, 2023 · 1 comment
Closed

ebs br: restore data should be after tikv nodes are all ready #5242

BornChanger opened this issue Aug 14, 2023 · 1 comment
Assignees
@WangLe1321 @BornChanger
Labels
area/ebs-br severity/major 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 45T cluster ebs restore

What did you expect to see?

Restore succeed

What did you see instead?

Restore failed and restore data goes behind of tikvs are ready

image
@BornChanger BornChanger mentioned this issue Aug 14, 2023
Closed
10 tasks
@BornChanger BornChanger self-assigned this Aug 14, 2023
@BornChanger
Copy link
Contributor Author

The TiKV was restarted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@WangLe1321 WangLe1321

@BornChanger BornChanger

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

Successfully merging a pull request may close this issue.

ebs br: check status of global nodes before doing data recovery BornChanger/tidb-operator
2 participants
@WangLe1321 @BornChanger