potiuk commented on issue #29149: URL: https://github.com/apache/airflow/issues/29149#issuecomment-1404282832
Additionally - why you do not want to disable scheduler? Seems like a reasonable "parameter" of your disaster recovery scenario where you would not start a scheduler, but everything else will be enabled (and you can switch this particular instance to be "working" by enabling scheduler. I think this kind of scenario is great to be handled by the way your deployment is running airlfow and "not running scheduler" seems like it achieves what you want. I am converting it to a discussion - but if you think there are other reasons why scheduler should be running while not doing scheduling, feel free to elaborate on it. -- 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-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
