ttl: force to kill SQL in scan task when canceling TTL job/task

[lcwangchao]

What problem does this PR solve?

Issue Number: close #56511

What changed and how does it work?

force to kill the TTL scan sql when cancelling TTL job/task

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.

TTL: force to kill the TTL scan sql when cancelling TTL job/task

[tiprow]

Hi @lcwangchao. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[codecov]

Codecov Report

Attention: Patch coverage is 91.66667% with 3 lines in your changes missing coverage. Please review.

Project coverage is 57.1784%. Comparing base (1eb0c8c) to head (037f74a).
Report is 140 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #56518         +/-   ##
=================================================
- Coverage   73.3698%   57.1784%   -16.1915%     
=================================================
  Files          1626       1776        +150     
  Lines        448852     642830     +193978     
=================================================
+ Hits         329322     367560      +38238     
- Misses        99364     250787     +151423     
- Partials      20166      24483       +4317     

Flag	Coverage Δ
integration	38.6551% <0.0000%> (?)
unit	73.1433% <91.6666%> (+0.6801%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.9478% <ø> (ø)
parser	∅ <ø> (∅)
br	52.4870% <ø> (+6.9101%)	⬆️

[YangKeao]

LGTM

[bb7133]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bb7133, YangKeao

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:

• OWNERS [YangKeao,bb7133]

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]

[LGTM Timeline notifier]

Timeline:

• 2024-10-10 07:14:50.064585104 +0000 UTC m=+1116645.484798108: ☑️ agreed by YangKeao.
• 2024-10-10 17:17:13.039286285 +0000 UTC m=+1152788.459499296: ☑️ agreed by bb7133.

[lcwangchao]

/retest

[tiprow]

@lcwangchao: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[lcwangchao]

/retest

[tiprow]

@lcwangchao: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[hawkingrei]

/retest

[lcwangchao]

/retest

[tiprow]

@lcwangchao: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.1: #56576.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #56577.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #56578.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.4: #56959.

[ti-chi-bot]

In response to a cherrypick label: cannot checkout release-8.5: error checking out release-8.5: exit status 1. output: error: pathspec 'release-8.5' did not match any file(s) known to git