statistics: do not block when sending analyze result

[Rustin170506]

What problem does this PR solve?

Issue Number: close #51993

Problem Summary:

See: #51993 (comment)

What changed and how does it work?

We should check if errExitCh is already closed, then we don't need to block sending the analyzed result.

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.

修复自动分析在 OOM 后卡住的问题
Fix Auto-Analysis stuck issue after OOM

[codecov]

Codecov Report

Merging #52107 (a7b0d47) into master (75c8347) will decrease coverage by 15.7525%.
Report is 17 commits behind head on master.
The diff coverage is 66.6666%.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #52107         +/-   ##
=================================================
- Coverage   70.6807%   54.9282%   -15.7525%     
=================================================
  Files          1486       1603        +117     
  Lines        439452     612626     +173174     
=================================================
+ Hits         310608     336505      +25897     
- Misses       109337     252919     +143582     
- Partials      19507      23202       +3695     

Flag	Coverage Δ
integration	36.9002% <0.0000%> (?)
unit	70.5934% <66.6666%> (+0.1016%)	⬆️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	51.9642% <ø> (+6.1454%)	⬆️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AilinKid, hawkingrei

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 [AilinKid,hawkingrei]

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-03-26 10:19:52.66780389 +0000 UTC m=+1976819.690050278: ☑️ agreed by hawkingrei.
• 2024-03-27 08:18:27.423464773 +0000 UTC m=+2055934.445711160: ☑️ agreed by AilinKid.

[Rustin170506]

/retest

[hawkingrei]

/cherrypick release-7.5

[ti-chi-bot]

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

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.

[winoros]

/cherrypick release-7.1

[ti-chi-bot]

@winoros: new pull request created to branch release-7.1: #52616.

In response to this:

/cherrypick release-7.1

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.