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

[GitBox <gi...@apache.org>]

gvazharov edited a comment on issue #15369:
URL: https://github.com/apache/airflow/issues/15369#issuecomment-820516076


   Hi @kaxil, neither in the UI, nor in the database something was in running state, I've checked all database tables for something that on first look could cause the problem, but found nothing disturbing..
   
   I have deleted the failed task instance from the UI, because there was some timeout error, which was caused from another services, all previous executions of this dag were successful and I had only 1 failed instance that was irrelevant for me, that's why I removed it in order the UI to be clear and if any relevant new error dag runs occur to see them straight.
   
   That's right, I guessed also that their shouldn't be any connection between the tast_instance table with the other once, but somehow because the execution_time + dag_id exist in the following tables task_instace, dag_run, log and rendered_task_instance_fields thought that probably in the background Airflow make some relation between them.
   
   For me was also interesting to find how are the [currently_active_runs](https://github.com/apache/airflow/blob/beb8af5ac6c438c29e2c186145115fb1334a3735/airflow/jobs/scheduler_job.py#L1696) set, but didn't manage to do that, wanted to know if some kind of query is made to the database, that calculates their sum and if yes, how this query looks like.
   


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