Skip to content

br: reused table id is disabled when restore a brand-new cluster (#41358)#41404

Closed
ti-chi-bot wants to merge 17 commits intopingcap:release-6.6from
ti-chi-bot:cherry-pick-41358-to-release-6.6
Closed

br: reused table id is disabled when restore a brand-new cluster (#41358)#41404
ti-chi-bot wants to merge 17 commits intopingcap:release-6.6from
ti-chi-bot:cherry-pick-41358-to-release-6.6

Conversation

@ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #41358

What problem does this PR solve?

Issue Number: close #41333

Problem Summary:
when restoring to a brand-new cluster, reused table id was disabled, which caused restore to consume more resources.

What is changed and how it works?

Check List

Tests

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

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
Copy link
Member Author

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Details

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/cherry-pick-not-approved labels Feb 14, 2023
@ti-chi-bot ti-chi-bot added component/br This issue is related to BR of TiDB. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. type/cherry-pick-for-release-6.6 labels Feb 14, 2023
@fengou1
Copy link
Contributor

fengou1 commented Feb 14, 2023

already cherry-picked by #41402

@fengou1 fengou1 closed this Feb 14, 2023
@VelocityLight VelocityLight added cherry-pick-approved Cherry pick PR approved by release team. and removed do-not-merge/cherry-pick-not-approved cherry-pick-approved Cherry pick PR approved by release team. labels Feb 15, 2023
@ti-chi-bot ti-chi-bot deleted the cherry-pick-41358-to-release-6.6 branch April 15, 2025 08:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cherry-pick-approved Cherry pick PR approved by release team. component/br This issue is related to BR of TiDB. release-note-none Denotes a PR that doesn't merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants