[AIRFLOW-6014] reschedule deleted pending tasks#7611
Closed
inytar wants to merge 1 commit intoapache:masterfrom
wooga:6014-reschedule-deleted-pending-tasks
Closed
[AIRFLOW-6014] reschedule deleted pending tasks#7611inytar wants to merge 1 commit intoapache:masterfrom wooga:6014-reschedule-deleted-pending-tasks
inytar wants to merge 1 commit intoapache:masterfrom
wooga:6014-reschedule-deleted-pending-tasks
Conversation
This code checks if a k8s process has been deleted and was in the pending state, if so it will reschedule the task.
Contributor
Author
|
A alternative version in #6606 has already been merged. |
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
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 code checks if a k8s process has been deleted and was in the
pending state, if so it will reschedule the task.
This is an alternative implementation of #6606, which we have been using internally. I don't have any preference on which PR to use, wanted to show what we have been running in production for some time.
Issue link: AIRFLOW-6014
Make sure to mark the boxes below before creating PR: [x]
[AIRFLOW-NNNN]. AIRFLOW-NNNN = JIRA ID*KubernetesJobWatchers, and it requires a lot of k8s api knowledge it seems, I would be happy with some help on moving forward with this.* For document-only changes commit message can start with
[AIRFLOW-XXXX].In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.