arunravimv commented on issue #37154:
URL: https://github.com/apache/airflow/issues/37154#issuecomment-1925372542

   Adding some additional info, scheduler logs keeps logging. We run scheduler 
in HA with 2 replica and our backed store in MYSQL from AWS RDS.
   ```
   [2024-02-03T15:14:13.171+0000] {scheduler_job_runner.py:1433} INFO - DAG 
mapped_task_issue scheduling was skipped, probably because the DAG record was 
locked
   ```
   
   We are new to Airflow Source code, but we saw this [possible 
area](https://github.com/apache/airflow/blob/d987bce144ac8e42bd269e1971d0ad4f15dcff95/airflow/ti_deps/deps/prev_dagrun_dep.py#L83)
 where the problem might be originating from. The _count_unsuccessful_tis func 
in PrevDagrunDep Class only considers SKIPPED and SUCCESS as successful state, 
but I believe in this case REMOVED is also a valid successful state. 
   
   However we don't know why the lasted dag run is not getting marked as failed 
here with [unmet dependency error 
here](https://github.com/apache/airflow/blob/d987bce144ac8e42bd269e1971d0ad4f15dcff95/airflow/ti_deps/deps/prev_dagrun_dep.py#L181)
 and why is it in stuck state


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to