Resolving streampark flink on k8s that flink task status is failed but k8s pod still alive #3634
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Resolving streampark flink on k8s that flink task status is failed but k8s pod still alive
What changes were proposed in this pull request
Issue Number: close #3618
The status of flink task is failed or other end state in database, but is running in memory, which lead to show failed in streampark but is running actually.
This change reslove the streampark flink status and the real task status not consistent.
Brief change log
Remove the check and return that state on database is end state then not update the state.
Verifying this change
Show in #3618
Does this pull request potentially affect one of the following parts