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

TiKV failed for more than 5 minutes, and the system did not set the backup task as failed [restore for 5439] #5812

Open
ti-chi-bot opened this issue Oct 25, 2024 · 1 comment
Assignees
Labels
area/ebs-br type/bug Something isn't working

Comments

@ti-chi-bot
Copy link
Member

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?

  1. let TiKV failed for more than 5 minutes,
  2. do volumebackup

What did you expect to see?

  1. if br can not connect tikv for more than 5 minutes, backup task should be set failed

What did you see instead?

  1. br always retrying
    img_v3_025q_30f8114c-54c1-4f3a-809a-986f46fba11g
    img_v3_025q_b371bbfe-b01a-4434-8a75-209f1909512g
@ti-chi-bot ti-chi-bot added area/ebs-br type/bug Something isn't working labels Oct 25, 2024
@ti-chi-bot
Copy link
Member Author

This issue is restored for #5439, it originally created at 2023-12-04 07:48:34.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ebs-br type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants