[
https://issues.apache.org/jira/browse/AIRFLOW-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043698#comment-16043698
]
ASF subversion and git services commented on AIRFLOW-1024:
----------------------------------------------------------
Commit 7af20fe452bad36767c43720168b5a34ce69eb0a in incubator-airflow's branch
refs/heads/master from [~aoen]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=7af20fe ]
[AIRFLOW-1024] Ignore celery executor errors (#49)
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.
Closes #2355 from aoen/ddavydov--
handle_celery_executor_errors_gracefully
> 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
> Fix For: 1.8.1
>
>
> 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)
