Versions Compared

Old Version 4

changes.mady.by.user Unknown User (criccomini)

Saved on

compared with

New Version 5

changes.mady.by.user Unknown User (criccomini)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

For this reason a "SCHEDULED" state is proposed in one of the PRs. This will not fully close the door to this race condition due to the fact that TaskInstance evaluate their own state in case of UP_FOR_RETRY (ie. checking if they should run now). Normally one would move this check to the scheduler was it not for that fact that we have backfills...

Pools

ll All tasks used to start with State.NONE. Unknown User (bolke)'s latest PR (AIRFLOW-128) introduces State.SCHEDULED when the TI has been created by the scheduler but not yet run. When the executor loads a TI, it eventually calls TI.run() which does one of two things:

...