statistics: rightly deal with timout when to send sync load (#57712)#57753
statistics: rightly deal with timout when to send sync load (#57712)#57753ti-chi-bot wants to merge 1 commit intopingcap:release-7.1from
Conversation
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@ti-chi-bot: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
This is an automated cherry-pick of #57712
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
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.