You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@airflow.apache.org by Emmanuel Brard <em...@getyourguide.com> on 2019/09/12 15:38:18 UTC

How does manage_sla works

Hello,

I am trying to understand the *manage_sla* code, because a daily (midnight
- UTC) DAG that we have, has an end task with a SLA of *timedelta(hours=4)*,
so I would expect the SLA to trigger if the task is still running after 4am
but it doesn't trigger.

I was therefore wondering why in the code here
<https://github.com/apache/airflow/blob/f497d1d5aad9d88d6c1cd1dfa28546e7a8c5cb5f/airflow/jobs/scheduler_job.py#L429>,
there is this initial offset by one next schedule date?

Trying the code, with this line commented, would trigger the expected SLA
miss...

Something we miss in the understanding?

Thanks a lot,
Emmanuel

-- 








GetYourGuide AG

Stampfenbachstrasse 48  

8006 Zürich

Switzerland



 <https://www.facebook.com/GetYourGuide>  
<https://twitter.com/GetYourGuide>  
<https://www.instagram.com/getyourguide/>  
<https://www.linkedin.com/company/getyourguide-ag>  
<http://www.getyourguide.com>