pingcap / pingcap/tidb-operator

Kill warmup pod when do volume restore, warmup pod will not be restarted, which will cause restore failed [restore for 5235]

Open
#5,794 1 comment 0 reactions 1 assignee View on GitHub

@BornChanger is already working on this.

Since Oct 25, 2024.

area/ebs-br type/bug
Dominant language
Go
Stars
1.3k
Forks
540
Avg merge
3d 2h
Merged PRs (30d)
18

Description

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. do volumerestore
  2. kill warmup pod

What did you expect to see?

  1. warmup pod will be restarted
  2. volume restore will success

What did you see instead?

  1. warmup pod will not be restarted
    371440f3-415e-4892-ac7f-0fa29c52b564

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.