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.

Sign up for GitHub

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

Jump to bottom

too many logs when full restore failed #51572

Closed
Leavrth opened this issue Mar 7, 2024 · 1 comment · Fixed by #51578
Closed

too many logs when full restore failed #51572

Leavrth opened this issue Mar 7, 2024 · 1 comment · Fixed by #51578
Labels
affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-7.1 This bug affects the 7.1.x(LTS) versions. affects-7.5 This bug affects the 7.5.x(LTS) versions. component/br This issue is related to BR of TiDB. severity/major type/bug The issue is confirmed as a bug.

Comments

@Leavrth
Copy link
Contributor

Leavrth commented Mar 7, 2024

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. full restore with coarse-grained and failed to ingest at last

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

  1. gracefully exits

3. What did you see instead (Required)

  1. too many logs print

4. What is your TiDB version? (Required)

master
@Leavrth Leavrth added type/bug The issue is confirmed as a bug. severity/major component/br This issue is related to BR of TiDB. labels Mar 7, 2024
@Leavrth Leavrth mentioned this issue Mar 7, 2024
Merged
13 tasks
@Leavrth Leavrth added affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-7.1 This bug affects the 7.1.x(LTS) versions. affects-7.5 This bug affects the 7.5.x(LTS) versions. and removed may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.1 may-affects-6.5 may-affects-7.1 may-affects-7.5 labels Mar 11, 2024
@Leavrth
Copy link
Contributor Author

Leavrth commented Mar 11, 2024 •
edited
Loading

cherry-pick because this PR also removes some redundant logs

ti-chi-bot bot pushed a commit that referenced this issue Mar 12, 2024
@Leavrth
br: stop log when full restore failed (#51578)
d604b06 
close #51572
@ti-chi-bot ti-chi-bot mentioned this issue Mar 26, 2024
Merged
13 tasks
ti-chi-bot bot pushed a commit that referenced this issue Mar 29, 2024
@ti-chi-bot
br: stop log when full restore failed (#51578) (#52104)
cc3e77d 
close #51572
This was referenced Apr 7, 2024
Merged
Merged
@Oreoxmt Oreoxmt mentioned this issue Apr 8, 2024
Merged
18 tasks
ti-chi-bot bot pushed a commit that referenced this issue Apr 17, 2024
@ti-chi-bot
br: stop log when full restore failed (#51578) (#52375)
853d735 
close #51572
ti-chi-bot bot pushed a commit that referenced this issue May 22, 2024
@ti-chi-bot
br: stop log when full restore failed (#51578) (#52376)
5efe65e 
close #51572
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-7.1 This bug affects the 7.1.x(LTS) versions. affects-7.5 This bug affects the 7.5.x(LTS) versions. component/br This issue is related to BR of TiDB. severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

br: stop log when full restore failed Leavrth/tidb
1 participant
@Leavrth