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

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

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

[AIRFLOW-2178] Add handling on SLA miss errors

Closes #3173 from d3cay1/airflow2178-master


> Scheduler can't get past SLA check if SMTP settings are incorrect
> -----------------------------------------------------------------
>
>                 Key: AIRFLOW-2178
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2178
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: 1.9.0
>         Environment: 16.04
>            Reporter: James Meickle
>            Assignee: David Klosowski
>            Priority: Major
>         Attachments: log.txt
>
>
> After testing Airflow for a while in staging, I provisioned our prod cluster 
> and enabled the first DAG on it. The "backfill" for this DAG performed just 
> fine, so I assumed everything was working and left it over the weekend.
> However, when the last "backfill" period completed and the scheduler 
> transitioned to the most recent execution date, it began failing in the 
> `manage_slas` method. Due to a configuration difference, SMTP was timing out 
> in production, preventing the SLA check from ever completing; this both 
> blocked SLA notifications, as well as prevented further tasks in this DAG 
> from ever getting scheduled.
> As an operator, I would expect AIrflow to treat scheduling tasks as a 
> higher-priority concern, and to do so even f the SLA feature fails to work. I 
> would also expect Airflow to notify me in the web UI that email sending is 
> not currently working.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to