-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
BACKUP SQL Command returns size of 0 #27247
Comments
/assign @fengou1 |
The root cause of the problem is that we get the total size via a key named Lines 509 to 510 in f7fdffc
...but we recorded the size with other keys, we can record the same data with key Line 269 in 550c7d0
|
Please edit this comment or add a new comment to complete the following informationNot a bug
Duplicate bug
BugNote: Make Sure that 'component', and 'severity' labels are added 1. Root Cause Analysis (RCA) (optional)2. Symptom (optional)3. All Trigger Conditions (optional)4. Workaround (optional)5. Affected versions6. Fixed versions |
Bug Report
1. Minimal reproduce step (Required)
(1) start a TiDB cluster locally through tiup
(2) generate some data before backup
I used the following script to generate around 5 million records
(3) use SQL command to backup
2. What did you expect to see? (Required)
After the BACKUP is finished, it should return info about the BACKUP whose size is bigger than 0.
3. What did you see instead (Required)
The backup took 9.04 seconds and the "Size" is 0, while I could see the backup file in folder /tmp/backup0816/full and I could use these files to retore to a new constructed empty TiDB cluster using SQL command RESTORE DATABASE * FROM 'local:///tmp/backup0816/full';
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: