karenbraganz commented on issue #52711: URL: https://github.com/apache/airflow/issues/52711#issuecomment-3098222775
@Mzhussiyev @vishwasarunkumar regarding suggestions for mitigating this issue- you will first need to identify why the DAGs are getting deactivated. Are you seeing any error messages in the logs around the time of the deactivation? For example, if you see import or processor timeouts, you could increase the [dagbag_import_timeout](https://airflow.apache.org/docs/apache-airflow/2.11.0/configurations-ref.html#dagbag-import-timeout) and [dag_file_processor_timeout](https://airflow.apache.org/docs/apache-airflow/2.11.0/configurations-ref.html#dag-file-processor-timeout). @Mzhussiyev regarding your second question about the D1 and D2 DAGs, I recommend [starting a discussion thread ](https://github.com/apache/airflow/discussions/new/choose) for that since it is not related to this topic. It is possible that some of your Airflow or worker configurations are limiting the number of DAGs or tasks that can run concurrently on the environment. -- 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]
