You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/11/05 09:25:11 UTC

[GitHub] [airflow] stijndehaes commented on issue #19421: Airflow 2.2.1 upgrade

stijndehaes commented on issue #19421:
URL: https://github.com/apache/airflow/issues/19421#issuecomment-961742890


   By looking through the source code I noticed this can happen when you have task instances that have no dag run attached. This means these are orphaned task instances, in theory one could created the needed dag run but this does not look to be easily feasible. I also noticed that some of the task instances are of deleted/renamed dags so it's impossible to generate a proper dag run.
   
   I think these orphaned task instances can get into the database by dag renaming or deleting a dag in the UI, but the dag file was still on disk and thus reparsed by the scheduler. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org