airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fokko Driesprong (JIRA)" <>
Subject [jira] [Resolved] (AIRFLOW-2178) Scheduler can't get past SLA check if SMTP settings are incorrect
Date Wed, 04 Apr 2018 07:22:00 GMT


Fokko Driesprong resolved AIRFLOW-2178.
       Resolution: Fixed
    Fix Version/s: 2.0.0

Issue resolved by pull request #3173

> Scheduler can't get past SLA check if SMTP settings are incorrect
> -----------------------------------------------------------------
>                 Key: AIRFLOW-2178
>                 URL:
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: 1.9.0
>         Environment: 16.04
>            Reporter: James Meickle
>            Assignee: David Klosowski
>            Priority: Major
>             Fix For: 2.0.0
>         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

View raw message