[ 
https://issues.apache.org/jira/browse/AIRFLOW-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963508#comment-15963508
 ] 

ASF subversion and git services commented on AIRFLOW-276:
---------------------------------------------------------

Commit 0a5fb7856b545073516210fcfc369d2072823ae9 in incubator-airflow's branch 
refs/heads/v1-8-test from [~sekikn]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=0a5fb78 ]

[AIRFLOW-1004][AIRFLOW-276] Fix `airflow webserver -D` to run in background

AIRFLOW-276 introduced a monitor process for gunicorn
to find new files in the dag folder, but it also changed
`airflow webserver -D`'s behavior to run in foreground.
This PR fixes that by running the monitor as a daemon
process.

Closes #2208 from sekikn/AIRFLOW-1004

(cherry picked from commit a9b20a04b052e9479dbb79fd46124293085610e9)


> 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.15#6346)

Reply via email to