Skip to content

Conversation

@okJiang
Copy link
Member

@okJiang okJiang commented Nov 4, 2025

What problem does this PR solve?

Issue Number: close #64257

Problem Summary:

The scan region here is a batch. BR will retry this batch scan region.

  • Expectation: If an error is reported in every retry, the whole batch scan region should be retreated to the leader handle.
  • Now, when an error retry is encountered, the first scan region in the loop will be retreated, but when err is changed to nil in the first retreated scan region, the retreated will be canceled. The first scan region will be retreated, but the first time the scan region is retreated, err is changed to nil, so the retreated region is canceled, which is not as expected.

What changed and how does it work?

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

@ti-chi-bot ti-chi-bot bot added do-not-merge/needs-tests-checked release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Nov 4, 2025
@codecov
Copy link

codecov bot commented Nov 4, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.9027%. Comparing base (749c973) to head (efdd992).
⚠️ Report is 24 commits behind head on master.

Additional details and impacted files
@@               Coverage Diff                @@
##             master     #64259        +/-   ##
================================================
+ Coverage   72.7381%   74.9027%   +2.1645%     
================================================
  Files          1859       1884        +25     
  Lines        503905     519506     +15601     
================================================
+ Hits         366531     389124     +22593     
+ Misses       115136     106659      -8477     
- Partials      22238      23723      +1485     
Flag Coverage Δ
integration 48.8456% <100.0000%> (?)
unit 72.6339% <100.0000%> (+0.3263%) ⬆️

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

Components Coverage Δ
dumpling 52.8700% <ø> (ø)
parser ∅ <ø> (∅)
br 63.3997% <100.0000%> (+17.0143%) ⬆️
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@okJiang
Copy link
Member Author

okJiang commented Nov 4, 2025

/retest

2 similar comments
@okJiang
Copy link
Member Author

okJiang commented Nov 4, 2025

/retest

@okJiang
Copy link
Member Author

okJiang commented Nov 4, 2025

/retest

}, backoffer)

return lastRegions, err
return lastRegions, retryErr
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
return lastRegions, retryErr
return lastRegions, retryErr

should better use last error, or the error stack will be very large.

@okJiang
Copy link
Member Author

okJiang commented Nov 4, 2025

/retest

@ti-chi-bot ti-chi-bot bot added approved needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Nov 7, 2025
@ti-chi-bot
Copy link

ti-chi-bot bot commented Nov 7, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 3pointer, rleungx

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:

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 ti-chi-bot bot added lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Nov 7, 2025
@ti-chi-bot
Copy link

ti-chi-bot bot commented Nov 7, 2025

[LGTM Timeline notifier]

Timeline:

  • 2025-11-07 06:55:24.153330368 +0000 UTC m=+425973.596360247: ☑️ agreed by 3pointer.
  • 2025-11-07 08:18:22.49041611 +0000 UTC m=+430951.933445989: ☑️ agreed by rleungx.

@ti-chi-bot
Copy link

ti-chi-bot bot commented Nov 7, 2025

@okJiang: 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
idc-jenkins-ci-tidb/unit-test efdd992 link unknown /test unit-test

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved lgtm release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

BR scan region unable to properly fallback to leader handle

3 participants