Re: Airflow SLA shows tasks that doesn't miss SLA

[siddharth anand <sa...@apache.org>]

We have been using run the SLA_miss_callback feature for over 6 months
now... for our hourly DAGs. We tend to miss SLAs (and rightly so) about 20%
of the time. We haven't seen this bug. We are also running on the hour
boundaries and not at 59 minutes from the hour. Is there are reason your
start_date is not rounded to the hour boundaries?

-s

On Thu, Jul 14, 2016 at 12:39 AM, Rendy Bambang Junior <
rendy.b.junior@gmail.com> wrote:

> I did some experiment by defining 1 hour (timedelta(hours=1)) SLA for my
> hourly dag (59 * * * *), and see Browse > SLA Misses.
>
> Somehow it shows some items do not even have 1 hour difference between
> execution date and timestamp. For example
>
>    - execution date 07-14T05:59:00
>    - timestamp 07-14T06:23:21.568905
>
> Differences between those to is only ~24 minutes (those number is taken
> from Browse > SLA Misses from airflow UI).
>
> How it should be configured? Did I miss something?
> Rendy
>