br: Change default check point lag limit

[BornChanger]

What problem does this PR solve?

Issue Number: ref #50803

Problem Summary:

What changed and how does it work?

This PR set the default value of 'check-point-lag-limit' to 24 hours, and also expose the paramter.

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

[tiprow]

Hi @BornChanger. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

[codecov]

Codecov Report

Merging #51906 (fe7a656) into master (490e17c) will decrease coverage by 16.0871%.
The diff coverage is 0.0000%.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #51906         +/-   ##
=================================================
- Coverage   70.6676%   54.5805%   -16.0871%     
=================================================
  Files          1481       1592        +111     
  Lines        439252     608909     +169657     
=================================================
+ Hits         310409     332346      +21937     
- Misses       109334     253347     +144013     
- Partials      19509      23216       +3707     

Flag	Coverage Δ
integration	36.4606% <0.0000%> (?)

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

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	51.4020% <0.0000%> (+5.5430%)	⬆️

[BornChanger]

/cc @3pointer @RidRisR @YuJuncen

[ti-chi-bot]

@BornChanger: GitHub didn't allow me to request PR reviews from the following users: RidRisR.

Note that only pingcap members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @3pointer @RidRisR @YuJuncen

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.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-03-25 04:08:38.20302805 +0000 UTC m=+1868145.225274438: ☑️ agreed by YuJuncen.
• 2024-03-25 05:23:04.573175049 +0000 UTC m=+1872611.595421437: ☑️ agreed by Leavrth.

[tiprow]

@BornChanger: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
fast_test_tiprow	ebbbabd	link	true	/test fast_test_tiprow

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[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

[BornChanger]

/hold

[BornChanger]

/type cherry-pick-for-release-8.0

[ti-chi-bot]

@BornChanger: The label(s) type/cherry-pick-release-8.0 cannot be applied, because the repository doesn't have them.

In response to this:

/type cherry-pick-release-8.0

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.

[BornChanger]

/type cherry-pick-for-release-6.5

[BornChanger]

/type cherry-pick-for-release-7.1

[BornChanger]

/type cherry-pick-for-release-7.5

[BornChanger]

/remove-type cherry-pick-for-release-8.0

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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