+1 to renaming dagrun_timeout and to adding a true execution_timeout on the
DAG. In the meantime, I've opened a PR [1] to clarify the current behavior
in the relevant docstring.
[1] https://github.com/apache/airflow/pull/4782
individual tasks after the run has timed-out, without them just
immediately getting cancelled and timed-out. Perhaps a new TaskDep, as those
can already be ignored?
-ash
> On 15 Feb 2019, at 07:19, vardangupta...@gmail.com wrote:
>
> Hi team,
>
> We wanted to enable dag_run timeou
<>
On Fri, Feb 15, 2019 at 12:49 PM vardangupta...@gmail.com <
vardangupta...@gmail.com> wrote:
> Hi team,
>
> We wanted to enable dag_run timeouts on our dags but when we have gone
> through the behavior of how dagrun_timeout works, we got to know, it only
> works o
Hi team,
We wanted to enable dag_run timeouts on our dags but when we have gone through
the behavior of how dagrun_timeout works, we got to know, it only works on when
below conditions are met.
1) dagrun should be scheduled one i.e. not manually created
2) max_active_runs must be configured
