autoid_service: remove the force rebase on close behavior

[tiancaiamao]

What problem does this PR solve?

Issue Number: ref #38442
close #53393

Problem Summary:

What changed and how does it work?

The original design is that we try our best to avoid holes in AUTO_ID_CACHE=1,
so when autoid leader exit, forceRebase is called to return the non-consumed in memory IDs back.

When there are a lot of tables, this operation could not be finish quickly.
And tidb graceful shutdown can not done within 30s. This cause tidb can not restart quickly to provide service.

We think over it and deside to remove the force rebase on close behavior.

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.

No unit test apply here (it requires tidb restart to cover the changes).
Some integration test may notice the change.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors

Behavior change, not tidb restart can cause hole in auto id allocating using AUTO_ID_CACHE=1

• 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 @tiancaiamao. 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.5497%. Comparing base (5d27b73) to head (39eee29).
Report is 16 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #53315        +/-   ##
================================================
+ Coverage   72.4973%   74.5497%   +2.0523%     
================================================
  Files          1497       1497                
  Lines        429959     429984        +25     
================================================
+ Hits         311709     320552      +8843     
+ Misses        98996      89535      -9461     
- Partials      19254      19897       +643     

Flag	Coverage Δ
integration	48.9945% <ø> (?)
unit	71.3025% <ø> (-0.0919%)	⬇️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	50.1806% <ø> (+8.7515%)	⬆️

[bb7133]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bb7133, Defined2014

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:

• pkg/autoid_service/OWNERS [bb7133]

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-17 07:12:10.583660354 +0000 UTC m=+1810084.340795928: ☑️ agreed by bb7133.
• 2024-05-17 08:45:54.512209004 +0000 UTC m=+1815708.269344574: ☑️ agreed by Defined2014.

[ti-chi-bot]

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