After br failure, the volumebackup status was not immediately set to failed [restore for 52243]

Open

#56,845 opened on Oct 25, 2024 1 comment 0 reactions 1 assignee Claimed by @BornChanger View on GitHub

component/br type/bug

Dominant language: Go
Stars: 40.5k
Forks: 6.2k
PR merge metrics: PR metrics pending

Description

## Bug Report

Please answer these questions before submitting your issue. Thanks!

### 1. Minimal reproduce step (Required)
1. do rolling restart
2. do volumebackup

### 2. What did you expect to see? (Required)
1. volumebackup success
2. The pause schedule lasts for a short period of time

### 3. What did you see instead (Required)
1. volumebackup is stuck, when exceed Volume Backup Init Job Max Active Seconds, volumebackup is set to failed
![image](https://github.com/pingcap/tidb/assets/81375082/fe2493c0-7cb1-4a3d-8bdc-8f1a72239951)
![image](https://github.com/pingcap/tidb/assets/81375082/c8e880d1-d9b8-411d-8ee6-5250e19aaff5)
![image](https://github.com/pingcap/tidb/assets/81375082/8afcc20d-2566-4f41-96c6-c11c8b7e570e)
![image](https://github.com/pingcap/tidb/assets/81375082/7bf40102-3cfe-4cd0-bedd-ab99c727bf64)

### 4. What is your TiDB version? (Required)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

After br failure, the volumebackup status was not immediately set to failed [restore for 52243]

Description

Contributor guide

Assessment

Get new issues in your inbox