You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2018/09/02 18:05:04 UTC
[jira] [Assigned] (AIRFLOW-2307) Airflow should track Celery task
ID
[ https://issues.apache.org/jira/browse/AIRFLOW-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Apache Spark reassigned AIRFLOW-2307:
-------------------------------------
Assignee: (was: Holden Karau's magical unicorn)
> Airflow should track Celery task ID
> -----------------------------------
>
> Key: AIRFLOW-2307
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2307
> Project: Apache Airflow
> Issue Type: Improvement
> Components: scheduler
> Affects Versions: 1.9.0
> Reporter: John Arnold
> Priority: Minor
>
> For celery executor, airflow keeps the AsyncResult in memory for the duration of the task, then deletes when task completes (success or fail).
> This can make troubleshooting failed tasks hard – trying to figure out which task instance is which "celery task" in Flower, etc.
> It would be a lot easier if there was a "Task Instance id" that could be populated with the AsyncResult.id for celery, or otherwise a UID for other executors.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)