br: fix checkpoint cannot advance after pause->stop->start

[RidRisR]

What problem does this PR solve?

Issue Number: close #53047
Problem Summary:

What changed and how does it work?

When advancer stop a task, the isPaused would be marked as false

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.

fix when checkpoint cannot advance after pause->stop->start

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.0338%. Comparing base (b421b72) to head (307e8c9).
Report is 21 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #53091        +/-   ##
================================================
+ Coverage   72.0329%   75.0338%   +3.0008%     
================================================
  Files          1499       1510        +11     
  Lines        431222     441565     +10343     
================================================
+ Hits         310622     331323     +20701     
+ Misses       101291      89560     -11731     
- Partials      19309      20682      +1373     

Flag	Coverage Δ
integration	50.3267% <66.6666%> (?)
unit	71.2547% <100.0000%> (+0.0250%)	⬆️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	56.1613% <100.0000%> (+17.8154%)	⬆️

[YuJuncen]

rest lgtm

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Leavrth, YuJuncen

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:

• br/OWNERS [Leavrth,YuJuncen]

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-05-08 02:16:17.915988658 +0000 UTC m=+1014731.673124226: ☑️ agreed by Leavrth.
• 2024-05-08 03:03:24.443290652 +0000 UTC m=+1017558.200426225: ☑️ agreed by YuJuncen.

[hawkingrei]

/ok-to-test

[RidRisR]

/test check_dev2

[ti-chi-bot]

@RidRisR: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test build
• /test check-dev
• /test check-dev2
• /test mysql-test
• /test pull-br-integration-test
• /test pull-integration-ddl-test
• /test pull-lightning-integration-test
• /test pull-mysql-client-test
• /test unit-test

The following commands are available to trigger optional jobs:

• /test canary-notify-when-compatibility-sections-changed
• /test pingcap/tidb/canary_ghpr_unit_test
• /test pull-common-test
• /test pull-e2e-test
• /test pull-integration-common-test
• /test pull-integration-copr-test
• /test pull-integration-jdbc-test
• /test pull-integration-mysql-test
• /test pull-integration-nodejs-test
• /test pull-sqllogic-test
• /test pull-tiflash-test

Use /test all to run the following jobs that were automatically triggered:

• pingcap/tidb/ghpr_build
• pingcap/tidb/ghpr_check
• pingcap/tidb/ghpr_check2
• pingcap/tidb/ghpr_mysql_test
• pingcap/tidb/ghpr_unit_test
• pingcap/tidb/pull_br_integration_test
• pingcap/tidb/pull_integration_ddl_test
• pingcap/tidb/pull_mysql_client_test

In response to this:

/test check_dev2

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.

[RidRisR]

/test check-dev2

[tiprow]

@RidRisR: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test check_dev2

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-sigs/prow repository.

[tiprow]

@RidRisR: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test check-dev2

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-sigs/prow repository.

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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