Update compatibility of BR (#5905)#5968
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
|
@YuJuncen please accept the invitation then you can push to the cherry-pick pull requests. |
|
/ho;d |
|
/hold |
Well, what should I do... (Maybe make another PR? Or can we just regenerate this invite link?) |
|
/cherry-pick-invite |
Because #5802 is still pending. @3pointer has not decided whether to cherry-pick this content to v4.0. |
|
@TomShawn Got it, let's keep holding this. |
|
/cherry-pick-invite 🤯 |
|
/cherry-pick-invite |
|
@zhouqiang-cl please accept the invitation then you can push to the cherry-pick pull requests. |
|
/cherry-pick-invite |
|
@YuJuncen please accept the invitation then you can push to the cherry-pick pull requests. |
|
|
||
| | 功能 | 相关 issue | 解决方式 | | ||
| | ---- | ---- | ----- | | ||
| | 聚簇索引 | [#565](https://github.com/pingcap/br/issues/565) | 确保备份时 tidb_enable_clustered_index 全局变量和恢复时一致,否则会导致数据不一致的问题,例如 `default not found` 和数据索引不一致。 | |
There was a problem hiding this comment.
Please remove v5.0-releated content in this PR.
| | 备份版本(纵向) \ 恢复版本(横向) | 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) 问题) | |
There was a problem hiding this comment.
Please remove the v5.0-related content.
There was a problem hiding this comment.
I think those can be reserved, because the user of v4.0 can also use v5.0 clusters, and wondering the compatibility between them. 🤔
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
|
/unhold |
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. DetailsReviewer can indicate their review by writing |
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: c8ddd59 |
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/5968After apply modifications, you can push your change to this PR via:
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)