[Fix] Manually trigger savepoint and save after success #4280
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
I have a question. After the savepoint is successful, the disk has already been stored here， and there are no issues with the 2.1.6 verification @CuteShaos @wolfboys |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
I noticed that this issue has been fixed in previous versions, but I found that 2.1.6 still has this problem. Through Git history, I found that this part of the code was deleted later. What is the reason for this? Although it is difficult to use this feature frequently, when manually triggering savepoint, I found that there are operation logs but no savepoint path recorded, so I cannot use this savepoint to start the Flink task
What changes were proposed in this pull request
Issue Number: close #3493
Brief change log
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts