Skip to content

Update compatibility of BR (#5905)#5968

Merged
ti-chi-bot merged 5 commits into
pingcap:release-4.0from
ti-srebot:release-4.0-0b851ba263a9
Apr 12, 2021
Merged

Update compatibility of BR (#5905)#5968
ti-chi-bot merged 5 commits into
pingcap:release-4.0from
ti-srebot:release-4.0-0b851ba263a9

Conversation

@ti-srebot
Copy link
Copy Markdown
Contributor

@ti-srebot ti-srebot commented Apr 7, 2021

cherry-pick #5905 to release-4.0
You can switch your code base to this Pull Request by using git-extras:

# In docs-cn repo:
git pr https://github.com/pingcap/docs-cn/pull/5968

After apply modifications, you can push your change to this PR via:

git push git@github.com:ti-srebot/docs-cn.git pr/5968:release-4.0-0b851ba263a9

update compatibility of BR

First-time contributors' checklist

What is changed, added or deleted? (Required)

After introducing clustered index in 5.0, there are some new compatibility problems of BR.

Which TiDB version(s) do your changes apply to? (Required)

  • master (the latest development version)
  • v5.0 (TiDB 5.0 versions)
  • v4.0 (TiDB 4.0 versions)
  • v3.1 (TiDB 3.1 versions)
  • v3.0 (TiDB 3.0 versions)
  • v2.1 (TiDB 2.1 versions)

Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot ti-srebot mentioned this pull request Apr 7, 2021
7 tasks
@ti-srebot ti-srebot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. type/cherry-pick-for-release-4.0 This PR is cherry-picked to release-4.0 from a source PR. labels Apr 7, 2021
@ti-srebot ti-srebot requested review from TomShawn and overvenus April 7, 2021 03:11
@ti-srebot
Copy link
Copy Markdown
Contributor Author

@YuJuncen please accept the invitation then you can push to the cherry-pick pull requests.
https://github.com/ti-srebot/docs-cn/invitations

@ti-chi-bot ti-chi-bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Apr 7, 2021
@TomShawn
Copy link
Copy Markdown
Contributor

TomShawn commented Apr 7, 2021

/ho;d

@TomShawn
Copy link
Copy Markdown
Contributor

TomShawn commented Apr 7, 2021

/hold

@ti-chi-bot ti-chi-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 7, 2021
@YuJuncen
Copy link
Copy Markdown
Contributor

YuJuncen commented Apr 8, 2021

Sorry, we couldn't find that repository invitation. It is possible that the invitation was revoked or that you are not logged into the invited account.

Well, what should I do... (Maybe make another PR? Or can we just regenerate this invite link?)

@YuJuncen
Copy link
Copy Markdown
Contributor

YuJuncen commented Apr 9, 2021

/cherry-pick-invite

@TomShawn
Copy link
Copy Markdown
Contributor

TomShawn commented Apr 9, 2021

Sorry, we couldn't find that repository invitation. It is possible that the invitation was revoked or that you are not logged into the invited account.

Well, what should I do... (Maybe make another PR? Or can we just regenerate this invite link?)

Because #5802 is still pending. @3pointer has not decided whether to cherry-pick this content to v4.0.

@YuJuncen
Copy link
Copy Markdown
Contributor

YuJuncen commented Apr 9, 2021

@TomShawn Got it, let's keep holding this.

@YuJuncen
Copy link
Copy Markdown
Contributor

YuJuncen commented Apr 9, 2021

/cherry-pick-invite

🤯

@zhouqiang-cl
Copy link
Copy Markdown
Contributor

/cherry-pick-invite

@ti-srebot
Copy link
Copy Markdown
Contributor Author

@zhouqiang-cl please accept the invitation then you can push to the cherry-pick pull requests.
https://github.com/ti-srebot/docs-cn/invitations

@YuJuncen
Copy link
Copy Markdown
Contributor

YuJuncen commented Apr 9, 2021

/cherry-pick-invite

@ti-srebot
Copy link
Copy Markdown
Contributor Author

@YuJuncen please accept the invitation then you can push to the cherry-pick pull requests.
https://github.com/ti-srebot/docs-cn/invitations

Comment thread br/backup-and-restore-tool.md Outdated

| 功能 | 相关 issue | 解决方式 |
| ---- | ---- | ----- |
| 聚簇索引 | [#565](https://github.com/pingcap/br/issues/565) | 确保备份时 tidb_enable_clustered_index 全局变量和恢复时一致,否则会导致数据不一致的问题,例如 `default not found` 和数据索引不一致。 |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Please remove v5.0-releated content in this PR.

Comment thread br/backup-and-restore-tool.md Outdated
Comment on lines +85 to +90
| 备份版本(纵向) \ 恢复版本(横向) | BR nightly / TiDB nightly | BR v5.0 / TiDB v5.0| BR v4.0 / TiDB v4.0 |
| ---- | ---- | ---- | ---- |
| **BR nightly / TiDB nightly** | ✅ | ✅ | ✅ |
| **BR v5.0 / TiDB v5.0** | ✅ | ✅ | ✅
| **BR v4.0 / TiDB v4.0** | ❌(如果恢复了使用非整数类型聚簇主键的表到 v4.0 的 TiDB 集群,BR 会无任何警告地导致数据错误) | ❌(如果恢复了使用非整数类型聚簇主键的表到 v4.0 的 TiDB 集群,BR 会无任何警告地导致数据错误) | ✅(如果 TiKV >= v4.0.0-rc.1,BR 包含 [#233](https://github.com/pingcap/br/pull/233) Bug 修复,且 TiKV 不包含 [#7241](https://github.com/tikv/tikv/pull/7241) Bug 修复,那么 BR 会导致 TiKV 节点重启) |
| **BR nightly 或 v5.0 / TiDB v4.0** | ❌(当 TiDB < v4.0.9 时会出现 [#609](https://github.com/pingcap/br/issues/609) 问题) | ❌(当 TiDB < v4.0.9 会出现 [#609](https://github.com/pingcap/br/issues/609) 问题) | ❌(当 TiDB < v4.0.9 会出现 [#609](https://github.com/pingcap/br/issues/609) 问题) |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Please remove the v5.0-related content.

Copy link
Copy Markdown
Contributor

@YuJuncen YuJuncen Apr 12, 2021

Choose a reason for hiding this comment

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

I think those can be reserved, because the user of v4.0 can also use v5.0 clusters, and wondering the compatibility between them. 🤔

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@overvenus @IANTHEREAL PTAL, thanks~

@ti-chi-bot ti-chi-bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Apr 12, 2021
Comment thread br/backup-and-restore-tool.md Outdated
Comment thread br/backup-and-restore-tool.md Outdated
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
@TomShawn
Copy link
Copy Markdown
Contributor

/unhold
/lgtm

@ti-chi-bot ti-chi-bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 12, 2021
@ti-chi-bot
Copy link
Copy Markdown
Member

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • TomShawn

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 writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Apr 12, 2021
@TomShawn
Copy link
Copy Markdown
Contributor

/merge

@ti-chi-bot
Copy link
Copy Markdown
Member

This pull request has been accepted and is ready to merge.

DetailsCommit hash: c8ddd59

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

Labels

size/S Denotes a PR that changes 10-29 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT1 Indicates that a PR has LGTM 1. type/cherry-pick-for-release-4.0 This PR is cherry-picked to release-4.0 from a source PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants