Matt, have you set this parameter in your config file? https://github.com/apache/incubator-airflow/blob/7d95a0dca06505a224e43aa8f767ce8b7d15e99e/airflow/configuration.py#L230
On 10 March 2017 at 13:23, Matt Martin <[email protected]> wrote: > Thanks for the reply Jason. We could definitely do that when we have a > more formal deployment process (i.e. automatically restart the webserver > whenever a deploy is done). For initial testing, however, we have left the > DAG folder open to all of our initial testers even though most of them > don't have the permissions needed to restart the associated airflow > services. Perhaps the way we've set things up is just an airflow > anti-pattern that should be avoided? > > Also, I've been told this delay is due to the fact that webserver caches > DAGs because parsing/processing DAGs is expensive. Is it the actual > parsing/processing of DAGs that is expensive? Or is it the scanning of the > filesystem for changed files that is expensive? If it's the latter, then > the usage of inotify seems like it'd be particularly beneficial. > > Appreciate your thoughts. Thanks again! > Matt > -- Im Xuan Ji!
