Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix ApiException handling when adopting completed pods #41109

Merged
merged 2 commits into from
Jul 31, 2024

Conversation

jedcunningham
Copy link
Member

When trying to complete adopted pods, if we encounter an ApiException, we should assume we were unable to adopt the pod meaning we shouldn't add that to our running set. If we do, running can fill up over time with tasks the executor isn't actually watching.

cc @wolfier

When trying to complete adopted pods, if we encounter an ApiException,
we should assume we were unable to adopt the pod meaning we shouldn't
add that to our `running` set. If we do, `running` can fill up over time
with tasks the executor isn't actually watching.
@boring-cyborg boring-cyborg bot added area:providers provider:cncf-kubernetes Kubernetes provider related issues labels Jul 30, 2024
@jedcunningham jedcunningham merged commit b014077 into apache:main Jul 31, 2024
63 checks passed
@jedcunningham jedcunningham deleted the ke_adoption_running branch July 31, 2024 12:16
molcay pushed a commit to VladaZakharova/airflow that referenced this pull request Aug 19, 2024
When trying to complete adopted pods, if we encounter an ApiException,
we should assume we were unable to adopt the pod meaning we shouldn't
add that to our `running` set. If we do, `running` can fill up over time
with tasks the executor isn't actually watching.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:providers provider:cncf-kubernetes Kubernetes provider related issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants