log backup: set a proper maxVersion to resolve lock

[3pointer]

What problem does this PR solve?

Issue Number: close #57134

Problem Summary:

1. See issue.

What changed and how does it work?

To minimize the risk of lock conflicts, set the maxVersion to be the largest existing version value across all slow regions, incremented by 1. This adjustment helps optimize RPO by proactively reducing lock contention.

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.8203%. Comparing base (87669fb) to head (7e8d4c4).
Report is 126 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #57178        +/-   ##
================================================
+ Coverage   73.0633%   74.8203%   +1.7569%     
================================================
  Files          1659       1705        +46     
  Lines        458027     468795     +10768     
================================================
+ Hits         334650     350754     +16104     
+ Misses       102843      96141      -6702     
- Partials      20534      21900      +1366     

Flag	Coverage Δ
integration	49.3121% <0.0000%> (?)
unit	72.3731% <100.0000%> (+0.0365%)	⬆️

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

Components	Coverage Δ
dumpling	52.7673% <ø> (-0.1806%)	⬇️
parser	∅ <ø> (∅)
br	61.0989% <100.0000%> (+15.3786%)	⬆️

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BornChanger, 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 [BornChanger,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-11-07 02:45:48.07396117 +0000 UTC m=+1095460.913116709: ☑️ agreed by YuJuncen.
• 2024-11-11 01:54:42.631941205 +0000 UTC m=+234844.822810198: ☑️ agreed by BornChanger.

[BornChanger]

/retest

[tiprow]

@BornChanger: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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]

@3pointer: You cannot manually add or delete the cherry pick branch category labels. It will be added automatically by bot when the PR is created.

In response to adding label named type/cherry-pick-for-release-6.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.

[ti-chi-bot]

@3pointer: You cannot manually add or delete the cherry pick branch category labels. It will be added automatically by bot when the PR is created.

In response to adding label named type/cherry-pick-for-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.

[ti-chi-bot]

@3pointer: You cannot manually add or delete the cherry pick branch category labels. It will be added automatically by bot when the PR is created.

In response to adding label named type/cherry-pick-for-release-8.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.

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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