-
Notifications
You must be signed in to change notification settings - Fork 499
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
br: logStop not working #5249
Comments
I try to add |
I also encountered this problem |
The log backup is running in TiKV (in the background), currently, it doesn't support to be stopped via Backup CR. |
@fanjlii I have found a way how to stop it. By using tidb community tollkit. |
|
what is the status of this issue. Is it planned to be fixed ? |
Can you stop the log backup if the Backup CR is still exist? ref https://docs.pingcap.com/tidb-in-kubernetes/stable/backup-to-aws-s3-using-br#stop-log-backup |
It works only if log backup is in running state. if log backup reaches an error state, setting logStop to true does nothing. Given that there is no way to know the status log backup (outside of tiup) logStop isn't very useful |
Bug Report
What version of Kubernetes are you using?
1.27
What version of TiDB Operator are you using?
1.5.0
What storage classes exist in the Kubernetes cluster and what are used for PD/TiKV pods??
do-block-storage (default), do-block-storage-retain, do-block-storage-xfs , do-block-storage-xfs-retain
What's the status of the TiDB cluster pods?
All Running
What did you do?
What did you expect to see?
Backup state stopped
What did you see instead?
Error: It supports single stream log task currently: [BR:Stream:ErrStreamLogTaskExist]stream task already exists
I see in my S3 the backup is still running. But i can't debug and make it stop.
The text was updated successfully, but these errors were encountered: