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 6319218635 for ; Fri, 31 Jul 2015 14:41:12 +0000 (UTC) Received: (qmail 26870 invoked by uid 500); 31 Jul 2015 14:41:12 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 26833 invoked by uid 500); 31 Jul 2015 14:41:12 -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 26822 invoked by uid 99); 31 Jul 2015 14:41:12 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Jul 2015 14:41:12 +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 D67D1C13CB for ; Fri, 31 Jul 2015 14:41:11 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.77 X-Spam-Level: * X-Spam-Status: No, score=1.77 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id XzxHGypI2TXF for ; Fri, 31 Jul 2015 14:41:08 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with SMTP id 494C920559 for ; Fri, 31 Jul 2015 14:41:07 +0000 (UTC) Received: (qmail 25590 invoked by uid 99); 31 Jul 2015 14:41:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Jul 2015 14:41:05 +0000 Date: Fri, 31 Jul 2015 14:41:05 +0000 (UTC) From: "Peeyush Bishnoi (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FALCON-1231) Improve JobCompletionNotification Service 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-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649294#comment-14649294 ] Peeyush Bishnoi commented on FALCON-1231: ----------------------------------------- [~pallavi.rao] After going through the details for the Oozie callback action, it looks like that this will send the post workflow details of Falcon instance to JMS directly. Currently, in Falcon we are sending the post workflow details of Falcon instance to JMS through FalconPostProcessing class. So if we agree to create notification listener (approach 2 from FALCON-1313) for generating email notification, then we need to read the post workflow details received from JMS server of Oozie callback action. > Improve JobCompletionNotification Service > ----------------------------------------- > > Key: FALCON-1231 > URL: https://issues.apache.org/jira/browse/FALCON-1231 > Project: Falcon > Issue Type: Sub-task > Reporter: Pallavi Rao > Assignee: Pallavi Rao > Attachments: OozieJobStatusNotification.pdf > > > Workflow completion is currently dependent on post processing action putting messages (success/failure) to a JMS queue. > When failures occur on Hadoop / Oozie, the post processing action may not get executed either. In such cases, Falcon will be blind to the status of the workflow and re-tries will not happen. > Explore url notification of oozie to get job completion notifications. Fall back on polling when workflows run beyond SLA. -- This message was sent by Atlassian JIRA (v6.3.4#6332)