Return-Path: X-Original-To: apmail-falcon-dev-archive@minotaur.apache.org Delivered-To: apmail-falcon-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 464FB184DB for ; Tue, 27 Oct 2015 09:56:44 +0000 (UTC) Received: (qmail 73425 invoked by uid 500); 27 Oct 2015 09:56:43 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 73374 invoked by uid 500); 27 Oct 2015 09:56:43 -0000 Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@falcon.apache.org Delivered-To: mailing list dev@falcon.apache.org Received: (qmail 73360 invoked by uid 99); 27 Oct 2015 09:56:43 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Oct 2015 09:56:43 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 3502D1A2CA7 for ; Tue, 27 Oct 2015 09:56:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.79 X-Spam-Level: * X-Spam-Status: No, score=1.79 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id zNYSb1zqeg64 for ; Tue, 27 Oct 2015 09:56:28 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with SMTP id 0F70F237FD for ; Tue, 27 Oct 2015 09:56:28 +0000 (UTC) Received: (qmail 72352 invoked by uid 99); 27 Oct 2015 09:56:27 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Oct 2015 09:56:27 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id C18112C1F56 for ; Tue, 27 Oct 2015 09:56:27 +0000 (UTC) Date: Tue, 27 Oct 2015 09:56:27 +0000 (UTC) From: "Narayan Periwal (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FALCON-1495) In instance status list, show all runs for instances when requested by user MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FALCON-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976117#comment-14976117 ] Narayan Periwal commented on FALCON-1495: ----------------------------------------- [~pavan kumar], Addressed your review comments. Please have a look > In instance status list, show all runs for instances when requested by user > --------------------------------------------------------------------------- > > Key: FALCON-1495 > URL: https://issues.apache.org/jira/browse/FALCON-1495 > Project: Falcon > Issue Type: Sub-task > Components: ease, general > Reporter: sandeep samudrala > Assignee: Narayan Periwal > Attachments: FALCON-1495-v0.patch, FALCON-1495-v1.patch, FALCON-1495-v2.patch > > > Most of the times , when there are failures in the pipelines, retries run and the workflows might have got succeeded in sub sequential retry. But for end user to figure out why it has failed initially might be useful to understand for failures handling and SLA misses. > As of now to figure out the same, its a tedious task to get such information by either going through oozie DB/logs or via the logs backed up in hdfs by the falcon postprocessing(which is 100% reliable as in few cases, falcon post processing might fail or for some reason if it couldn't back up the logs). > In either case, Falcon should abstract the oozie client layer to be used by end user, and support all runs status to end user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)