[
https://issues.apache.org/jira/browse/AIRFLOW-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395722#comment-16395722
]
James Meickle commented on AIRFLOW-2178:
----------------------------------------
I also ran into this confusing failure state when I shipped an SLA miss
callback that threw an exception. The result is that nothing gets scheduled.
> 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
> 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)
