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/04/15 13:56:50 UTC

[GitHub] [airflow] gvazharov commented on issue #15369: Airflow 2.0 Scheduler suddenly stopped queuing tasks

gvazharov commented on issue #15369:
URL: https://github.com/apache/airflow/issues/15369#issuecomment-820442237


   Hi, 
   
   I've checked, they were no task instances in running state.
   
   I think the problem can be reproduced, when you delete a failed task instance from the UI. 
   At this point the task instance is deleted from the UI and from the Postgres task_instance table, but the data sets which are related to this deleted task_instance are not removed from the other postgres tables, such as dag_run, job, log and rendered_task_instance_fields. 
   For me exactly because of this reason, somehow airflow is thinking that this deleted task_instance is running, because it cannot be found in the task_instance table, but the execution_time and dag_id of this instance could be found in all other tables. 
   
   I am not quite sure if exactly this is the problem, but should be definitely directed in this way.
   
   As a solution of this problem I delete manually all data sets related to my dag from all postgres tables for the previous couple days(from the day, that the problem started to occur, till now) , started again the dag and the problem was solved.


-- 
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.

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