You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/10/06 00:27:20 UTC

[jira] [Commented] (AIRFLOW-548) Scheduler should be able run continously and pickup dags immediately by default

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

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

Commit fe5eaabb27136af3a3bc34521c85885b415d8246 in incubator-airflow's branch refs/heads/master from [~bolke]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=fe5eaab ]

[AIRFLOW-548] Load DAGs immediately & continually

A recent commit has changed the scheduler behavior
that it now
always stops after a specified period of time. The
operation scripts
(systemd etc) are not updated for this behavior
and many users actually
prefer to run the scheduler continously.

Secondly the default behavior was changed to not
pickup new DAGs
immediately, this has lead to confusion with
users.

Closes #1823 from bolkedebruin/fix_duration


> Scheduler should be able run continously and pickup dags immediately by default
> -------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-548
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-548
>             Project: Apache Airflow
>          Issue Type: Bug
>            Reporter: Bolke de Bruin
>            Assignee: Bolke de Bruin
>
> A recent commit has changed the scheduler behavior that it now always stops after a specified period of time. The operation scripts (systemd etc) are not updated for this behavior and many users actually prefer to run the scheduler continously.
> Secondly the scheduler doesn't pickup DAGs directly by default but after a set period of time. This has lead to confusion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)