airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Spark (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-2307) Airflow should track Celery task ID
Date Sun, 02 Sep 2018 18:05:04 GMT

    [ https://issues.apache.org/jira/browse/AIRFLOW-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16601533#comment-16601533
] 

Apache Spark commented on AIRFLOW-2307:
---------------------------------------

User 'johnarnold' has created a pull request for this issue:
https://github.com/apache/incubator-airflow/pull/3210

> 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)

Mime
View raw message