[
https://issues.apache.org/jira/browse/AIRFLOW-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16525541#comment-16525541
]
ASF subversion and git services commented on AIRFLOW-1840:
----------------------------------------------------------
Commit 859ec64aee98c0294229b3c29f57f3c89b6ad533 in incubator-airflow's branch
refs/heads/v1-10-test from [~ashb]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=859ec64 ]
[AIRFLOW-1840] Support back-compat on old celery config
The new names are in-line with Celery 4, but if
anyone upgrades Airflow
without following the UPDATING.md instructions
(which we probably assume
most people won't, not until something stops
working) their workers
would suddenly just start failing. That's bad.
This will issue a warning but carry on working as
expected. We can
remove the deprecation settings (but leave the
code in config) after
this release has been made.
Closes #3549 from ashb/AIRFLOW-1840-back-compat
(cherry picked from commit a4592f91eb125d7b463f1762fbfe0f64f7bc6b3a)
Signed-off-by: Bolke de Bruin <bo...@xs4all.nl>
> Fix Celery config
> -----------------
>
> Key: AIRFLOW-1840
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1840
> Project: Apache Airflow
> Issue Type: Bug
> Reporter: Fokko Driesprong
> Assignee: Fokko Driesprong
> Priority: Major
> Fix For: 1.10.0
>
>
> While configuring the Celery executor I keep running into this problem:
> ==> /var/log/airflow/scheduler.log <==
> Traceback (most recent call last):
> File
> "/usr/local/lib/python2.7/dist-packages/airflow/executors/celery_executor.py",
> line 83, in sync
> state = async.state
> File "/usr/local/lib/python2.7/dist-packages/celery/result.py", line 394,
> in state
> return self._get_task_meta()['status']
> File "/usr/local/lib/python2.7/dist-packages/celery/result.py", line 339,
> in _get_task_meta
> return self._maybe_set_cache(self.backend.get_task_meta(self.id))
> File "/usr/local/lib/python2.7/dist-packages/celery/backends/base.py", line
> 307, in get_task_meta
> meta = self._get_task_meta_for(task_id)
> AttributeError: 'DisabledBackend' object has no attribute '_get_task_meta_for'
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
