-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
br: update restore checkpoint information #18623
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Jianjun Liao <[email protected]>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Jianjun Liao <[email protected]>
|
||
PITR 恢复分为快照恢复和日志恢复两个阶段。 | ||
|
||
在第一次执行恢复时,br 工具会首先进入快照恢复阶段,这与上述只进行快照恢复操作相同。当 br 工具进入到快照恢复阶段,备份数据的上游集群的 ID 和备份数据的 BackupTS (等于日志恢复的起始时间点 `start-ts`)已经被记录于断点中。这意味着当恢复在快照恢复阶段执行失败时,尝试断点恢复继续时无法再调整快照备份路径(等于日志恢复的启示时间点 `restored-ts`). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
在第一次执行恢复时,br 工具会首先进入快照恢复阶段,这与上述只进行快照恢复操作相同。当 br 工具进入到快照恢复阶段,备份数据的上游集群的 ID 和备份数据的 BackupTS (等于日志恢复的起始时间点 `start-ts`)已经被记录于断点中。这意味着当恢复在快照恢复阶段执行失败时,尝试断点恢复继续时无法再调整快照备份路径(等于日志恢复的启示时间点 `restored-ts`). | |
在第一次执行恢复时,br 工具会首先进入快照恢复阶段,这与上述只进行快照恢复操作相同。当 br 工具进入到快照恢复阶段,备份数据的上游集群的 ID 和备份数据的 BackupTS (等于日志恢复的起始时间点 `start-ts`)已经被记录于断点中。这意味着当恢复在快照恢复阶段执行失败时,尝试断点恢复继续时无法再调整快照备份路径(等于日志恢复的起始时间点 `restored-ts`). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤔这句话有点绕
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 (in Chinese).
What is the related PR or file link(s)?
br: migrate pitr id map to the system table
mysql.tidb_pitr_id_map
tidb#55871Do your changes match any of the following descriptions?