Replies: 1 comment
-
|
it's may be due to too many dags or resources issue, share more info by running below commands airflow dags report or, you can let's try this, |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Issue with Dag Processor
Environment Details:
Cluster: AWS EKS Running on 1.35
Component: Dag Processor
Number of Dags: 900+
Airflow Version: 3.1.8
Instance Type: r7i.xlarge
Issue Observed:
No alive jobs found.I have recently deployed Airflox 3x. This is running on AWS EKS. The dag process is currently running with 2 replicas with below settings:
Every now and then the Dag Processor just keeping passing and failing causing the new dags and update to existing dags be not updated for several hours.
-- Snippet of Restarts --

Observation:
I do see that the dag processor is able to see the files in my dags folder but then it does not processor them. During dags update when I go inside the container and see the files, the files are updated files but when the jobs run on Airflow, it refers to the older version of the file which earlier had issues. So I have a feeling that the code is never registered or acknowledged by Airflow.
Any help on fixing this would be greatly appreciated. If I am missing any particular piece of information, please let me know.
Beta Was this translation helpful? Give feedback.
All reactions