arjunanan6 commented on issue #31679: URL: https://github.com/apache/airflow/issues/31679#issuecomment-1573647008
Indeed, I just correlated it (maybe incorrectly) to the continuous schedule. We are not using git-sync, however, a new build is triggered each time there is an update to our dags repository(ies). In this case, it is a dev environment, so it is just on a change to the dags directory. I find it weird that all other pods show the right status with the right DAGs, but scheduler didn't. Even an `airflow db reset` did not help - which makes sense considering that the scheduler had all the old DAGs in the dags dir. But anyway, I nuked the deployment for the scheduler and now things are behaving well. Thanks for the input, it helped me isolate the problem! -- 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]
