You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Aizhamal Nurmamat kyzy (JIRA)" <ji...@apache.org> on 2019/05/18 03:01:00 UTC
[jira] [Updated] (AIRFLOW-3413) Airflow sometimes doesn't know when
pod has completed when using KubernetesPodOperator.
[ https://issues.apache.org/jira/browse/AIRFLOW-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aizhamal Nurmamat kyzy updated AIRFLOW-3413:
--------------------------------------------
Labels: k (was: )
> Airflow sometimes doesn't know when pod has completed when using KubernetesPodOperator.
> ---------------------------------------------------------------------------------------
>
> Key: AIRFLOW-3413
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3413
> Project: Apache Airflow
> Issue Type: Bug
> Components: operators
> Affects Versions: 1.10.1
> Environment: Azure VM - Ubuntu 18.04.1 LTS - Docker CE 18.09.0
> Reporter: Trent Telfer
> Priority: Major
> Labels: k
>
> Currently running airflow in a docker container on an Ubuntu VM. When using the KubernetesPodOperator I get a condition where a pod will have completed on the kubernetes cluster but airflow still thinks it is running. The only way to get airflow to continue executing the task execution is to manually mark the pod as completed in airflow. I also attempted to use the dagrun_timeout which had no affect.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)