shahar1 commented on issue #70172: URL: https://github.com/apache/airflow/issues/70172#issuecomment-5038068580
> ### Description > When running a large, multi team airflow deployment with multiple stakeholder teams and lots of dags, finding time to schedule routine maintenance can be difficult, and we have to rely on agreements from the teams that Airflow will not be running at agreed times e.g. Saturday at 11am-12pm. > > ### Use case/motivation > I would like a screen added to the UI that calculates periods where no dags are running, i.e. 'maintenance windows' so that deployment managers of Airflow can calculate when maintenance periods should be scheduled. This is also useful for other engineers to calculate when systems Airflow is dependent on should have 'safe' downtime. > > ### Related issues > _No response_ > > ### Are you willing to submit a PR? > * [ ] Yes I am willing to submit a PR! > > ### Code of Conduct > * [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) Great idea! Keep in mind that practically there could be edge cases where there's no such window in practice (e.g., Dags that run once a minute), but: 1. It would be helpful to be aware of that, and maybe pre-calculate the "potential damage" (i.e., what Dags would be impacted due to the migration). 2. As an extension of this feature, maybe we could create a mechanism to prioritize tasks that have been on hold due to the maintenance window. -- 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]
