br: cluster in-place upgrade to v7.2.0 might encounter cross-version faulure. #20346
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ti-chi-bot
bot
added
missing-translation-status
hfxsd
reviewed
Feb 24, 2025
hfxsd
added
translation/done
hfxsd
added
the
area/br
hfxsd
reviewed
Feb 24, 2025
3pointer
approved these changes
Feb 24, 2025
hfxsd
approved these changes
Feb 24, 2025
ti-chi-bot
bot
added
lgtm
and removed
needs-1-more-lgtm
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hfxsd 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 |
BornChanger
reviewed
Feb 24, 2025
| @@ -145,9 +145,9 @@ This section introduces the BR compatibility information for all [Long-Term Supp | |||
|
|
|||
| > **Note:** | |||
| > | |||
| > Known issue: in v7.2.0, some system table fields are changed to case-sensitive, which might cause cross-version backup and restore failures. For more details, see [issue #43717](https://github.com/pingcap/tidb/issues/43717). | |||
| > Known issue: Starting from version v7.2.0, some system table fields in newly created clusters are case-sensitive. However, for clusters that are **upgraded online** from versions earlier than v7.2.0 to v7.2.0 or later, the corresponding system table fields remain case-insensitive. Backup and restore operations involving system tables between these two types of clusters might fail. For more details, see [Issue #43717](https://github.com/pingcap/tidb/issues/43717). | |||
There was a problem hiding this comment.
Suggested change
| > Known issue: Starting from version v7.2.0, some system table fields in newly created clusters are case-sensitive. However, for clusters that are **upgraded online** from versions earlier than v7.2.0 to v7.2.0 or later, the corresponding system table fields remain case-insensitive. Backup and restore operations involving system tables between these two types of clusters might fail. For more details, see [Issue #43717](https://github.com/pingcap/tidb/issues/43717). | |
| > Known issue: Starting from version v7.2.0, fields of some system tables in newly created clusters become case-sensitive. However, for clusters that are **upgraded online** from versions earlier than v7.2.0 to v7.2.0 or later, the corresponding fields remain case-insensitive. Restore with system tables from backup taken from clusters with those case-insensitive fields to clusters with the case-sensitive fields or vise verse will fail. For more details, see [Issue #43717](https://github.com/pingcap/tidb/issues/43717). |
ti-chi-bot
pushed a commit
to ti-chi-bot/docs
that referenced
this pull request
Feb 24, 2025
Signed-off-by: ti-chi-bot <[email protected]>
|
In response to a cherrypick label: new pull request created to branch |
Closed
16 tasks
|
In response to a cherrypick label: new pull request created to branch |
ti-chi-bot
pushed a commit
to ti-chi-bot/docs
that referenced
this pull request
Feb 24, 2025
Signed-off-by: ti-chi-bot <[email protected]>
Closed
16 tasks
|
In response to a cherrypick label: new pull request created to branch |
Merged
16 tasks
16 tasks
BornChanger
reviewed
Feb 24, 2025
|
|
||
| The following table lists the compatibility matrix for full backups: | ||
| The following table lists the compatibility matrix for full backups. Note that all data in the table comes from newly created clusters. |
There was a problem hiding this comment.
for clusters upgraded from version prior to v7.2.0 to v7.2.0 or above, their behavior is as of backup from v7.1.0.
BornChanger
reviewed
Feb 24, 2025
| @@ -156,7 +156,7 @@ The following table lists the compatibility matrix for full backups: | |||
| | v7.5.0 | v7.5.0 and later | - | | |||
| | v8.1.0 | v8.1.0 and later | - | | |||
|
|
|||
| The following table lists the compatibility matrix for log backups: | |||
| The following table lists the compatibility matrix for log backups. Note that all data in the table comes from newly created clusters. | |||
There was a problem hiding this comment.
for clusters upgraded from version prior to v7.2.0 to v7.2.0 or above, their behavior is as of backup from v7.1.0.
hfxsd
removed
needs-cherry-pick-release-7.5
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First-time contributors' checklist
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?