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

disttask/ddl: fix pause succeed task then run a new task (#47804) #47935

Merged

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #47804

What problem does this PR solve?

Issue Number: close #47805

Problem Summary:
The pause ddl job was triggered after the task was successfully completed, and at this point, the task had already been moved to the history table. After resuming the ddl, the table was not queried from the history table, resulting in the framework reopening the task and running it all over again.

What is changed and how it works?

  1. Use Channel to make sure the pause cmd actually works.
  2. Fetch task from global_task table and history table to make sure the task only run once.

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
  • No need to test
    • I checked and no code files have been changed.

Side effects

  • Performance regression: Consumes more CPU
  • Performance regression: Consumes more Memory
  • Breaking backward compatibility

Documentation

  • Affects user behaviors
  • Contains syntax changes
  • Contains variable changes
  • Contains experimental features
  • Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

optimize the pause&resume process when a dist task succeed.

@ti-chi-bot ti-chi-bot added ok-to-test Indicates a PR is ready to be tested. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. type/cherry-pick-for-release-7.5 This PR is cherry-picked to release-7.5 from a source PR. labels Oct 23, 2023
@ti-chi-bot ti-chi-bot added the cherry-pick-approved Cherry pick PR approved by release team. label Oct 23, 2023
@ywqzzy
Copy link
Contributor

ywqzzy commented Oct 23, 2023

/retest

2 similar comments
@ywqzzy
Copy link
Contributor

ywqzzy commented Oct 25, 2023

/retest

@ywqzzy
Copy link
Contributor

ywqzzy commented Oct 25, 2023

/retest

@ti-chi-bot ti-chi-bot bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Oct 25, 2023
Copy link
Collaborator

@Benjamin2037 Benjamin2037 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-chi-bot
Copy link

ti-chi-bot bot commented Oct 26, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Benjamin2037, ywqzzy

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added approved lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Oct 26, 2023
@ti-chi-bot
Copy link

ti-chi-bot bot commented Oct 26, 2023

[LGTM Timeline notifier]

Timeline:

  • 2023-10-25 14:14:14.665118471 +0000 UTC m=+2444052.252228617: ☑️ agreed by ywqzzy.
  • 2023-10-26 01:25:03.750499104 +0000 UTC m=+2484301.337609233: ☑️ agreed by Benjamin2037.

@hawkingrei
Copy link
Member

/retest

1 similar comment
@ywqzzy
Copy link
Contributor

ywqzzy commented Oct 26, 2023

/retest

@ywqzzy
Copy link
Contributor

ywqzzy commented Oct 26, 2023

/cherry-pick-invite

@ti-chi-bot
Copy link
Member Author

@ywqzzy Please accept the invitation then you can push to the cherry-pick pull requests.
Comment with "/cherry-pick-invite" if the invitation is expired.
https://github.com/ti-chi-bot/tidb/invitations

@ywqzzy
Copy link
Contributor

ywqzzy commented Oct 26, 2023

/hold

@ti-chi-bot ti-chi-bot bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 26, 2023
@ywqzzy
Copy link
Contributor

ywqzzy commented Oct 26, 2023

/retest

@ywqzzy
Copy link
Contributor

ywqzzy commented Oct 26, 2023

/unhold

@ti-chi-bot ti-chi-bot bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 26, 2023
@ti-chi-bot ti-chi-bot bot merged commit c5debb2 into pingcap:release-7.5 Oct 26, 2023
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved cherry-pick-approved Cherry pick PR approved by release team. lgtm ok-to-test Indicates a PR is ready to be tested. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. type/cherry-pick-for-release-7.5 This PR is cherry-picked to release-7.5 from a source PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants