A TiKV was restarted before it was stopped for scheduling, and BR did not exit in a timely manner and set the status to failed, resulting in the cluster remaining in the pause schedule state
zhongmin-amin opened this issue · 1 comments
zhongmin-amin commented
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?
- do rolling restart
- do volumebackup
What did you expect to see?
- volumebackup success
- The pause schedule lasts for a short period of time
What did you see instead?
- volumebackup is stuck, when exceed Volume Backup Init Job Max Active Seconds, volumebackup is set to failed
BornChanger commented
track and closed in tidb repo pingcap/tidb#52243