airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Serhii (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-1060) dag lost tracking the status of tasks and stuck in running state
Date Tue, 04 Apr 2017 16:39:41 GMT

    [ https://issues.apache.org/jira/browse/AIRFLOW-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955370#comment-15955370
] 

Serhii commented on AIRFLOW-1060:
---------------------------------

I have the same issue. It is 100% reproducible on 17.1.2 and 1.7.1.3 versions. If task takes
more 1 hour then subdag containing this task stucks in running state.

In logs for SubDagOperator I have found some mysterious error:
 
[2017-04-04 15:04:35,076] {jobs.py:965} ERROR - The airflow run command failed at reporting
an error. This should not occur in normal circumstances. Task state is 'running',reported
state is 'success'. TI is <TaskInstance: socrates_migration_etl.preparations.topoReports_prepare
2017-04-04 14:00:16.677858 [running]>

> dag lost tracking the status of tasks and stuck in running state
> ----------------------------------------------------------------
>
>                 Key: AIRFLOW-1060
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1060
>             Project: Apache Airflow
>          Issue Type: Bug
>            Reporter: Jeff Liu
>
> I'm running an airflow 1.7.1 in one of my environment and constantly run into an issue
with the main dag status stuck in "running" state, while the tasks all have completed successfully.
> To resolve the issue, I had to "delete" the dag entry in airflow UI, and re-run the job
manually so the dag job can recognize the tasks are all completed and set it self to successful
after re-run. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message