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

Posted to commits@airflow.apache.org by "Ash Berlin-Taylor (JIRA)" <ji...@apache.org> on 2019/02/11 11:43:00 UTC

[jira] [Resolved] (AIRFLOW-1524) Enquiry to understand Airflow Celery UI -> Browse -> Jobs UI and state

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

Ash Berlin-Taylor resolved AIRFLOW-1524.
----------------------------------------
    Resolution: Duplicate

> Enquiry to understand Airflow Celery UI -> Browse -> Jobs UI and state
> ----------------------------------------------------------------------
>
>                 Key: AIRFLOW-1524
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1524
>             Project: Apache Airflow
>          Issue Type: Task
>            Reporter: Prakash Kamani
>            Priority: Minor
>         Attachments: Capture.JPG
>
>
> We have Airflow Deployed in QA/STG and PROD env.
> In each of the environment, under Celery UI -> Browse -> Jobs option, we observe quite a few old job id in a running state even though there are no DAG in a running state.
> Can someone explain the purpose of this UI and reason for this behaviour.
> Please find attachment for the same for reference.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)