backup: check the store state by last heartbeat (#43099) #43213
Closed
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.
This is an automated cherry-pick of #43099
What problem does this PR solve?
Issue Number: close #42973
Problem Summary:
The current implementation cannot detect whether a store is down. So it keeps retry sending request to an offline store.
What is changed and how it works?
This PR checks the
LastHeartbeatTS
of the store and give up to request the store once the gap is greater than 20s (also defined in the PD package.)Check List
Tests
Backup over a cluster with one node down, finished in reasonable time.
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.