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

Posted to commits@airflow.apache.org by "Bolke de Bruin (JIRA)" <ji...@apache.org> on 2017/03/26 03:47:41 UTC

[jira] [Updated] (AIRFLOW-1024) Handle CeleryExecutor errors gracefully

     [ https://issues.apache.org/jira/browse/AIRFLOW-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bolke de Bruin updated AIRFLOW-1024:
------------------------------------
    Priority: Critical  (was: Major)

> Handle CeleryExecutor errors gracefully
> ---------------------------------------
>
>                 Key: AIRFLOW-1024
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1024
>             Project: Apache Airflow
>          Issue Type: Bug
>            Reporter: Dan Davydov
>            Priority: Critical
>
> If the Airflow celery executor receives a bad response from a worker (e.g. unpickled response), then it will crash the scheduler and cause it to restart.
> We should code defensively around the interactions with celery so that we just log errors instead of crashing the scheduler.
> It might makes sense to make the try catches one level higher (to catch errors from all executors), but this needs some investigation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)