*: fix 'Duplicate entry' error when @@auto_increment_increment and @@auto_increment_offset is set

[tiancaiamao]

What problem does this PR solve?

Issue Number: close #52622

Problem Summary:

What changed and how does it work?

1. set auto_increment_offset to 1 if its value is greater than auto_increment_increment
2. add more check to protect alloc.base from been change to a smaller value

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)

Follow the steps in the issue

• 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]

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

[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/test-infra repository.

[tiancaiamao]

@tangenta please also keep an eye on this.
We have several get auto_increment_increment and auto_increment_offset operation all over the codebase.
At a simple glance, AUTO_RANDOM also use those session variable, I'm not sure the behaviour of them for AUTO_RANDOM etc, so I do not change them in this commit. Maybe you can take a look for the other places.

[codecov]

Codecov Report

Merging #52626 (5f648b1) into master (3d82fc5) will increase coverage by 2.8187%.
Report is 19 commits behind head on master.
The diff coverage is 100.0000%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #52626        +/-   ##
================================================
+ Coverage   72.3590%   75.1777%   +2.8187%     
================================================
  Files          1470       1474         +4     
  Lines        427105     428189      +1084     
================================================
+ Hits         309049     321903     +12854     
+ Misses        98798      86010     -12788     
- Partials      19258      20276      +1018     

Flag	Coverage Δ
integration	50.4485% <94.7368%> (?)
unit	71.1754% <94.7368%> (-0.0751%)	⬇️

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

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

[tiancaiamao]

MySQL's document and implementation mismatch and it's a bug.
See https://bugs.mysql.com/bug.php?id=47118

We follow the MySQL document's.

[bb7133]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-04-17 14:00:28.634358678 +0000 UTC m=+433047.745405122: ☑️ agreed by Defined2014.
• 2024-04-18 05:43:09.991472216 +0000 UTC m=+489609.102518663: ☑️ agreed by bb7133.

[GMHDBJD]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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:

• OWNERS [Defined2014,GMHDBJD,bb7133]
• pkg/autoid_service/OWNERS [bb7133]
• pkg/table/OWNERS [GMHDBJD]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jackysp]

Why not backport this PR to the LTS branches?

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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