[
https://issues.apache.org/jira/browse/AIRFLOW-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Minghao Hu updated AIRFLOW-2007:
Description:
When I start to run a dag which contain only one task, the task failed
immediately and then become green later.
The task just call linux shell command to copy a big file from a folder to
another. When I start the task, it become red(failed)(meanwhile, the dagrun
become red too), but the "copy" process is running on the shell background
normally. Then because the dagrun failed, the dag starts the next dag run and
failed again.
After the process finished normally, the task become green but the dagrun don't.
Check:
1.I have checked the logs but there is no error log found.
2.After check the airflow database, I found task_instance table is inserted a
failed task record when the task starts. dag_run table is inserted a running
record. After a while the dag_run become failed.
3.For the job table, it is inserted a running record, and become success after
the shell command finished.(which is normally process)
My question:
1.Why the task failed immediately when it started.
2.Where does the airflow code modify the task_instance table?
> task failed first and then become green
> ---
>
> Key: AIRFLOW-2007
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2007
> Project: Apache Airflow
> Issue Type: Bug
> Components: DagRun
>Affects Versions: Airflow 1.7.1
>Reporter: Minghao Hu
>Priority: Blocker
>
> When I start to run a dag which contain only one task, the task failed
> immediately and then become green later.
> The task just call linux shell command to copy a big file from a folder to
> another. When I start the task, it become red(failed)(meanwhile, the dagrun
> become red too), but the "copy" process is running on the shell background
> normally. Then because the dagrun failed, the dag starts the next dag run and
> failed again.
> After the process finished normally, the task become green but the dagrun
> don't.
>
> Check:
> 1.I have checked the logs but there is no error log found.
> 2.After check the airflow database, I found task_instance table is inserted a
> failed task record when the task starts. dag_run table is inserted a running
> record. After a while the dag_run become failed.
> 3.For the job table, it is inserted a running record, and become success
> after the shell command finished.(which is normally process)
>
> My question:
> 1.Why the task failed immediately when it started.
> 2.Where does the airflow code modify the task_instance table?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
