[
https://issues.apache.org/jira/browse/AIRFLOW-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16409139#comment-16409139
]
ASF subversion and git services commented on AIRFLOW-1460:
----------------------------------------------------------
Commit 8c42d03c4e35a0046e46f0e2e6db588702ee7e8b in incubator-airflow's branch
refs/heads/master from [~tronbabylove]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=8c42d03 ]
[AIRFLOW-1460] Allow restoration of REMOVED TI's
When a task instance exists in the database but
its corresponding task
no longer exists in the DAG, the scheduler marks
the task instance as
REMOVED. Once removed, task instances stayed
removed forever, even if
the task were to be added back to the DAG.
This change allows for the restoration of REMOVED
task instances. If a
task instance is in state REMOVED but the
corresponding task is present
in the DAG, restore the task instance by setting
its state to NONE.
A new unit test simulates the removal and
restoration of a task from a
DAG and verifies that the task instance is
restored:
`./run_unit_tests.sh tests.models:DagRunTest`
JIRA:
https://issues.apache.org/jira/browse/AIRFLOW-1460
Closes #3137 from astahlman/airflow-1460-restore-
tis
> Tasks get stuck in the "removed" state
> --------------------------------------
>
> Key: AIRFLOW-1460
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1460
> Project: Apache Airflow
> Issue Type: Bug
> Reporter: George Leslie-Waksman
> Assignee: George Leslie-Waksman
> Priority: Major
> Fix For: 1.9.1
>
>
> The current handling of task instances that get assigned the state "removed"
> is that they get ignored.
> If the underlying task later gets re-added, the existing task instances will
> prevent the task from running in the future.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
