disttask/ddl: fail task for panic

[ywqzzy]

What problem does this PR solve?

Issue Number: close #48136

Problem Summary:
When operators for add index met some internal panic(possible when code have bugs or data corrupt), they will recover from panics since operators are running on workerpool.
Then the panics won't pass to the dist framework, then framework will mark subtasks which encountered panics as succeed.

What is changed and how it works?

Add recover for each operators of add index, cancel the pipeline when met panic.

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.

None

[tiprow]

Hi @ywqzzy. 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/test-infra repository.

[codecov]

Codecov Report

Merging #48135 (02015e2) into master (99a4f35) will increase coverage by 1.2447%.
Report is 3 commits behind head on master.
The diff coverage is 0.0000%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #48135        +/-   ##
================================================
+ Coverage   71.5999%   72.8447%   +1.2447%     
================================================
  Files          1400       1423        +23     
  Lines        405985     412715      +6730     
================================================
+ Hits         290685     300641      +9956     
+ Misses        95492      93187      -2305     
+ Partials      19808      18887       -921     

Flag	Coverage Δ
integration	42.3627% <0.0000%> (?)
unit	71.6497% <0.0000%> (+0.0498%)	⬆️

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

Components	Coverage Δ
dumpling	53.9874% <ø> (ø)
parser	∅ <ø> (∅)
br	48.9079% <ø> (-4.0166%)	⬇️

[ywqzzy]

/retest

[tiprow]

@ywqzzy: 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/test-infra repository.

[Benjamin2037]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [Benjamin2037,wjhuang2016]

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:

• 2023-10-31 11:09:15.278023361 +0000 UTC m=+2951352.865133508: ☑️ agreed by wjhuang2016.
• 2023-11-01 01:30:23.515066541 +0000 UTC m=+3003021.102176688: ☑️ agreed by Benjamin2037.

[hawkingrei]

/retest

[ti-chi-bot]

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