Skip to content
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: It shows "backup failed" when make a backup of empty DB, but the result $? is 0 #27466

Closed
joccau opened this issue Aug 21, 2021 · 3 comments · Fixed by #27467
Closed

br: It shows "backup failed" when make a backup of empty DB, but the result $? is 0 #27466

joccau opened this issue Aug 21, 2021 · 3 comments · Fixed by #27467
Labels
component/br This issue is related to BR of TiDB. severity/major sig/migrate type/bug The issue is confirmed as a bug.

Comments

@joccau
Copy link
Member

joccau commented Aug 21, 2021

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

(1) Create a database without table
(2) do the command:
./br backup db --db emptydb --pd "$ip:$port" --storage "local://$localDir"

2. What did you expect to see? (Required)

the result of "Database backup success summary" is expected and $? is 0

3. What did you see instead (Required)

[2021/08/21 12:29:09.666 +08:00] [INFO] [collector.go:66] ["Database backup failed summary"] [total-ranges=0] [ranges-succeed=0] [ranges-failed=0]

4. What is your TiDB version? (Required)

./br --version
Release Version: v5.2.0-alpha-696-g72be8ee
Git Commit Hash: 72be8ee
Git Branch: fix-retry-count
Go Version: go1.16.5
UTC Build Time: 2021-08-20 13:22:07
Race Enabled: false

@joccau joccau added the type/bug The issue is confirmed as a bug. label Aug 21, 2021
@joccau
Copy link
Member Author

joccau commented Aug 21, 2021

/sig migrate

@joccau
Copy link
Member Author

joccau commented Aug 21, 2021

/component br

@ti-srebot
Copy link
Contributor

Please edit this comment or add a new comment to complete the following information

Not a bug

  1. Remove the 'type/bug' label
  2. Add notes to indicate why it is not a bug

Duplicate bug

  1. Add the 'type/duplicate' label
  2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: #20100

1. Root Cause Analysis (RCA) (optional)

2. Symptom (optional)

3. All Trigger Conditions (optional)

4. Workaround (optional)

5. Affected versions

6. Fixed versions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/br This issue is related to BR of TiDB. severity/major sig/migrate type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants