[ https://issues.apache.org/jira/browse/AIRFLOW-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ash Berlin-Taylor closed AIRFLOW-1293. -------------------------------------- Resolution: Information Provided Anyone encountering this - a task going in to the Removed state means that _next time_ the DAG file parsed it was not there. Airflow will parse the DAG file many many times on the scheduler, and once for each task being executed on a worker, and the task generated need to be **stable** - you can't generate it just once and then never again. > Dynamically generated dependency job get marked as Removed state automatically > ------------------------------------------------------------------------------ > > Key: AIRFLOW-1293 > URL: https://issues.apache.org/jira/browse/AIRFLOW-1293 > Project: Apache Airflow > Issue Type: Bug > Affects Versions: 1.8.0 > Reporter: kenneth lam > Priority: Major > > In the dag, set up two task T1 >> T2. > while task id of T2 is not static as the task id is based on the ip address > of the running host. > As a result, airflow mark T2 as "Removed" and thus can't execute. > Although the dependency graph is constructed correctly in the web admin page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)