[
https://issues.apache.org/jira/browse/AIRFLOW-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15831585#comment-15831585
]
Chad T Henderson commented on AIRFLOW-276:
------------------------------------------
Considering https://issues.apache.org/jira/browse/AIRFLOW-758, would it not be
more straight forward to just revert back to execpv and run gunicorn with the
--reload argument? Granted, this functionality is listed under the "Debugging"
section of gunicorn's settings documentation, but it might be still be
appropriate for this use case. Link to gunicorn docs:
http://docs.gunicorn.org/en/19.0/settings.html#reload
> List of dags does not refresh in UI for a while
> -----------------------------------------------
>
> Key: AIRFLOW-276
> URL: https://issues.apache.org/jira/browse/AIRFLOW-276
> Project: Apache Airflow
> Issue Type: Improvement
> Reporter: Li Xuanji
> Assignee: Li Xuanji
> Priority: Minor
>
> After creating a new dag (eg by adding a file to `~/airflow/dags`), the web
> UI does not show the new for a while. It only shows it when either
> 1. gunicorn decides to restart the worker process, or
> 2. a scheduler picks up the new dag, adds it to the airflow db, and the web
> UI notices it in the db
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
