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

Scheduler won't resume if lightning exits abnormally #33546

Closed
rleungx opened this issue Mar 29, 2022 · 0 comments · Fixed by #33545
Closed

Scheduler won't resume if lightning exits abnormally #33546

rleungx opened this issue Mar 29, 2022 · 0 comments · Fixed by #33545
Labels
affects-5.2 This bug affects 5.2.x versions. affects-5.3 This bug affects 5.3.x versions. affects-5.4 This bug affects 5.4.x versions. affects-6.0 component/br This issue is related to BR of TiDB. component/pd severity/major type/bug The issue is confirmed as a bug.

Comments

@rleungx
Copy link
Member

rleungx commented Mar 29, 2022 •
edited
Loading

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. start a cluster with TiUP
  2. use lightning to import data
  3. kill lightning with kill -9

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

The schedulers are resumed after 5 minutes.

3. What did you see instead (Required)

The schedulers are paused after 5 minutes.

Screen Shot 2022-03-29 at 2 22 28 PM

4. What is your TiDB version? (Required)

master
@rleungx rleungx added the type/bug The issue is confirmed as a bug. label Mar 29, 2022
@rleungx rleungx mentioned this issue Mar 29, 2022
Merged
1 task
@glorv glorv added affects-5.2 This bug affects 5.2.x versions. affects-5.3 This bug affects 5.3.x versions. affects-5.4 This bug affects 5.4.x versions. affects-6.0 severity/major and removed severity/moderate labels Mar 29, 2022
@ti-chi-bot ti-chi-bot added may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. labels Mar 29, 2022
@glorv glorv removed may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. labels Mar 30, 2022
@glorv glorv mentioned this issue Mar 30, 2022
Open
@JmPotato JmPotato mentioned this issue Mar 31, 2022
Closed
ti-chi-bot pushed a commit that referenced this issue Apr 8, 2022
@rleungx
br: use the correct unit for pausing schedulers (#33545)
53042e7 
close #33546
This was referenced Apr 8, 2022
Closed
Merged
Merged
Closed
@sleepymole sleepymole mentioned this issue Apr 25, 2022
Closed
@tiancaiamao tiancaiamao added the component/br This issue is related to BR of TiDB. label Apr 27, 2022
ti-chi-bot pushed a commit that referenced this issue Apr 28, 2022
@ti-srebot
br: use the correct unit for pausing schedulers (#33545) (#33816)
a6848c4 
close #33546
@3pointer 3pointer mentioned this issue May 9, 2022
Merged
14 tasks
ti-chi-bot pushed a commit that referenced this issue Jun 15, 2022
@ti-srebot
br: use the correct unit for pausing schedulers (#33545) (#33815)
9b8d573 
close #33546
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affects-5.2 This bug affects 5.2.x versions. affects-5.3 This bug affects 5.3.x versions. affects-5.4 This bug affects 5.4.x versions. affects-6.0 component/br This issue is related to BR of TiDB. component/pd 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: use the correct unit for pausing schedulers rleungx/tidb
5 participants
@tiancaiamao @glorv @ChenPeng2013 @rleungx @ti-chi-bot