statistics: rightly deal with timout when to send sync load

[hawkingrei]

What problem does this PR solve?

Issue Number: close #57710

Problem Summary:

What changed and how does it work?

in the origin code, we can not check the timeout after sending the sync load. so it will block the sending sync load and take too much time.

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.

rightly deal with timout when to send sync load

正确处理发送 sync load 的超时

[hawkingrei]

/retest

[hawkingrei]

/retest

[hawkingrei]

/retest

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.6958%. Comparing base (feb34ec) to head (d1bf8b7).
Report is 3 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #57712        +/-   ##
================================================
+ Coverage   72.8160%   73.6958%   +0.8798%     
================================================
  Files          1677       1707        +30     
  Lines        464027     473720      +9693     
================================================
+ Hits         337886     349112     +11226     
+ Misses       105267     103088      -2179     
- Partials      20874      21520       +646     

Flag	Coverage Δ
integration	46.2147% <66.6666%> (?)
unit	72.2569% <100.0000%> (+0.0444%)	⬆️

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

Components	Coverage Δ
dumpling	52.7673% <ø> (ø)
parser	∅ <ø> (∅)
br	45.7186% <ø> (+0.0210%)	⬆️

[hawkingrei]

/retest

[purelind]

/retest

[hawkingrei]

/hold

[hawkingrei]

/unhold

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[time-and-fate]

/cherry-pick release-8.1-20241203-v8.1.1

[ti-chi-bot]

@time-and-fate: new pull request created to branch release-8.1-20241203-v8.1.1: #57931.

In response to this:

/cherry-pick release-8.1-20241203-v8.1.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.