backup: advacned prepare implementation (#48439)#52569
backup: advacned prepare implementation (#48439)#52569ti-chi-bot wants to merge 1 commit intopingcap:release-7.5from
Conversation
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
|
This cherry pick PR is for a release branch and has not yet been approved by triage owners. To merge this cherry pick:
DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
[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. |
|
@ti-chi-bot: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
@YuJuncen : Whats pending here. We are testing EBS BR on 7.5, so this is a critical PR for it. |
|
(This should have be brought to release-7.5 with another cherry-pick PR.) |
|
(it should be #50443) |
This is an automated cherry-pick of #48439
What problem does this PR solve?
Issue Number: close #50359
Problem Summary:
This PR implemented the client side of the enhanced prepare stage of snapshot backup.
What is changed and how it works?
Generally this is a state machine that tries to collect the whole range. If a region has applied to the last index, the region's range will be collected. When the whole key space has been collected, we are done.
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.