You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Bolke de Bruin (JIRA)" <ji...@apache.org> on 2017/03/26 04:07:42 UTC
[jira] [Closed] (AIRFLOW-962) Dag runs are deadlocked for DAG
scheduled for @once
[ https://issues.apache.org/jira/browse/AIRFLOW-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bolke de Bruin closed AIRFLOW-962.
----------------------------------
Resolution: Fixed
Assignee: Bolke de Bruin
Fix Version/s: 1.8.0
> Dag runs are deadlocked for DAG scheduled for @once
> ---------------------------------------------------
>
> Key: AIRFLOW-962
> URL: https://issues.apache.org/jira/browse/AIRFLOW-962
> Project: Apache Airflow
> Issue Type: Bug
> Components: DagRun
> Environment: airflow v1.7.1.3 installed AWS cluster node
> with celery executor ,rabbitMQ service and mysql for meta store
> Reporter: Sheikh Aslam Ahmed
> Assignee: Bolke de Bruin
> Fix For: 1.8.0
>
>
> We read mysql table row from python script and create dags out of it, any change in the row leads to change in the dag.
> we schedule dag based on inputs(like @once,hourly, daily etc).
> From last few days hourly and other scheduled profiles run properly but profile with schedule @once got failed (on web UI no task got picked up from the DAG). the error in the logs shows message as ' {jobs.py:538} ERROR - Dag runs are deadlocked for DAG: dagname'
> after that if we trigger a manual run for same DAG from web UI it run and complete successfully.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)