You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Linxiao Bai (JIRA)" <ji...@apache.org> on 2018/09/11 15:53:00 UTC
[jira] [Created] (AIRFLOW-3039) TriggerDagRunOperator jamming when
triggered concurrently
Linxiao Bai created AIRFLOW-3039:
------------------------------------
Summary: TriggerDagRunOperator jamming when triggered concurrently
Key: AIRFLOW-3039
URL: https://issues.apache.org/jira/browse/AIRFLOW-3039
Project: Apache Airflow
Issue Type: Bug
Components: DagRun
Affects Versions: 1.9.0
Environment: Linux, mysql
Reporter: Linxiao Bai
The error is caused when multiple independent TriggerDagRunOperator tasks pointing to the same dag.
When trigger concurrently, the target dag run instances will run sequentially instead of parallel.
The state is:
All dependencies are met but the task instance is not running...
I was able to get around with the issue by adding:
{code:java}
import random
import time
time.sleep(random.randint(1, 60))
{code}
before
{code:java}
airflow.operators.dagrun_operator.TriggerDagRunOperator.execute
{code}
as the first line.
The issue might be an executing_time related field has collision when update to the database.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)