executor: fix hang when the analyze worker unexpectedly exits

[hawkingrei]

What problem does this PR solve?

Issue Number: close #48356

Problem Summary:

What is changed and how it works?

if analyze worker or result handler unexpectedly exit. it is possible to hang in the place of sending 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.

None

[codecov]

Codecov Report

Merging #48365 (8709330) into master (8071fc7) will increase coverage by 1.7709%.
Report is 12 commits behind head on master.
The diff coverage is 77.7777%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #48365        +/-   ##
================================================
+ Coverage   71.3892%   73.1602%   +1.7709%     
================================================
  Files          1402       1425        +23     
  Lines        406861     416665      +9804     
================================================
+ Hits         290455     304833     +14378     
+ Misses        96465      93032      -3433     
+ Partials      19941      18800      -1141     

Flag	Coverage Δ
integration	43.9370% <55.5555%> (?)
unit	71.8243% <77.7777%> (+0.4350%)	⬆️

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

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

[Rustin170506]

Thanks!

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hi-rustin, winoros

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 [hi-rustin,winoros]

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-11-08 07:38:52.159968788 +0000 UTC m=+3629929.747078931: ☑️ agreed by winoros.
• 2023-11-08 10:12:21.840112722 +0000 UTC m=+3639139.427222867: ☑️ agreed by hi-rustin.

[hawkingrei]

/retest

[hawkingrei]

/cherrypick release-7.5

[ti-chi-bot]

@hawkingrei: new pull request created to branch release-7.5: #48445.

In response to this:

/cherrypick release-7.5

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 ti-community-infra/tichi repository.