You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/07/29 10:36:34 UTC
[GitHub] [airflow] mgorsk1 edited a comment on issue #17238: Unexpected skipped state for tasks run with KubernetesExecutor
mgorsk1 edited a comment on issue #17238:
URL: https://github.com/apache/airflow/issues/17238#issuecomment-889000426
Thanks for clarifing @jedcunningham completely agree, that log refers to pod state. But are there any scenarios if the task goes into `skipped` mode at all? From the docs I only saw this possible if we are explicitly raising AirflowSkipException in the task.
Although since task is in `skipped` phase in UI so the logs are not retrievable from UI, I found them on our S3 and this is what they say @ephraimbuddy:
**We are running single scheduler**.
Sometimes when I look into the NS where Airflow resides I see that some task pods are failing with following logs (but not sure if it's related):
which is werid cause the corresponding task in Airflow UI is marked as success (without retrying) and I can see logs from both Airflow worker and Kubernetes pod that was executed by it. Kubernetes monitoring shows that such pod indeed existed which makes the 404 more weird as I would only expect some race condition with 2+ schedulers, not single one.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org