There is a manual DAG refresh option in the UI for DAGs the UI is already
aware of -- this will reload a DAG. But that's not a complete solution to
the the more general DAG refresh problem.
-s
On Tue, Jun 20, 2017 at 6:36 PM, siddharth anand wrote:
> To clarify, at Agari, we use monitd (like sy
To clarify, at Agari, we use monitd (like systemd) to restart both
webserver and scheduler (running local executor) after deploying new dags
to the dag folder. The Web UI does not discover new DAGs and it does
automatically reload changes to existing files either.
-s
On Tue, Jun 20, 2017 at 6:34
We actually do restart both Web and Schedulers. I know the scheduler does
reparse the files in the dag folder, but the current state of the web ui
does require a restart.
-s
On Tue, Jun 20, 2017 at 6:07 PM, Ashika Umanga Umagiliya <
umanga@gmail.com> wrote:
> Greetings,
>
> We are using airf
Greetings,
We are using airflow (1.7) to manage our ETL pipeline and we are having
issues related to refreshing of DAGs.
When we update the DAG python script inside "dag folder" ,they don't get
updated in the UI.(DAG tree as well as the Code in the UI). We have to kill
and restart the "airflow we
