Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 7D708200C23 for ; Tue, 7 Feb 2017 22:53:47 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 7920D160B32; Tue, 7 Feb 2017 21:53:47 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C46E2160B3E for ; Tue, 7 Feb 2017 22:53:46 +0100 (CET) Received: (qmail 91276 invoked by uid 500); 7 Feb 2017 21:53:46 -0000 Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airflow.incubator.apache.org Delivered-To: mailing list commits@airflow.incubator.apache.org Received: (qmail 91259 invoked by uid 99); 7 Feb 2017 21:53:46 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Feb 2017 21:53:46 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 92315C0258 for ; Tue, 7 Feb 2017 21:53:45 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id BySz99kle4nu for ; Tue, 7 Feb 2017 21:53:45 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id C618F5F570 for ; Tue, 7 Feb 2017 21:53:44 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 10E55E026E for ; Tue, 7 Feb 2017 21:53:42 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id AAA1A25286 for ; Tue, 7 Feb 2017 21:53:41 +0000 (UTC) Date: Tue, 7 Feb 2017 21:53:41 +0000 (UTC) From: "Daniel Blazevski (JIRA)" To: commits@airflow.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AIRFLOW-849) Show whether spark job is "running" or "waiting" MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 07 Feb 2017 21:53:47 -0000 Daniel Blazevski created AIRFLOW-849: ---------------------------------------- Summary: Show whether spark job is "running" or "waiting" Key: AIRFLOW-849 URL: https://issues.apache.org/jira/browse/AIRFLOW-849 Project: Apache Airflow Issue Type: Improvement Reporter: Daniel Blazevski Priority: Minor As of now, Airflow shows that a task is "running" in Airflow when it could be listed as "WAITING" in the Spark UI (and can be listed as "WAITING" for hours when the Airflow UI might indicate it is running if I forget to check the Spark UI). Would be awesome once ticket 802 for spark integration is complete to add this enhancement of more granular detail about the task. -- This message was sent by Atlassian JIRA (v6.3.15#6346)