You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "arjunanan6 (via GitHub)" <gi...@apache.org> on 2023/06/02 10:43:57 UTC

[GitHub] [airflow] arjunanan6 commented on issue #31679: Issue with "@continuous" schedule.

arjunanan6 commented on issue #31679:
URL: https://github.com/apache/airflow/issues/31679#issuecomment-1573527092

   Hi @hussein-awala, sure here are the answers:
   1. We have only one scheduler.
   2. Actually, it is not. For some reason, the scheduler still has files from yesterday. I've tried deleting the scheduler pod, but it somehow has those retained. On the webserver pod for instance, I can see that the dag list is up to date.
   3. Seems to be, from the DB I can see that the last parsed time is from a few minutes ago. My change was first done about 3h back - when I first noticed this problem. 
   4. To be honest, it could be a total coincidence, but we only noticed this problem first after this switch to "@continuous" schedule in one DAG. At this moment, no new DAGs register at all, and I cannot remove anything either. This has to be related to pt. 2.


-- 
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: commits-unsubscribe@airflow.apache.org

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