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 9D98718A68 for ; Mon, 17 Aug 2015 19:29:08 +0000 (UTC) Received: (qmail 95718 invoked by uid 500); 17 Aug 2015 19:29:05 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 95676 invoked by uid 500); 17 Aug 2015 19:29:05 -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 95665 invoked by uid 99); 17 Aug 2015 19:29:05 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Aug 2015 19:29:05 +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 1B9831AA349 for ; Mon, 17 Aug 2015 19:29:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.794 X-Spam-Level: * X-Spam-Status: No, score=1.794 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-0.006] autolearn=disabled Received: from mx1-eu-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 bLcxSDKaCYl5 for ; Mon, 17 Aug 2015 19:28:51 +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 ED36120F4F for ; Mon, 17 Aug 2015 19:28:49 +0000 (UTC) Received: (qmail 92877 invoked by uid 99); 17 Aug 2015 19:28:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Aug 2015 19:28:46 +0000 Date: Mon, 17 Aug 2015 19:28:46 +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=14700086#comment-14700086 ] Peeyush Bishnoi commented on FALCON-1231: ----------------------------------------- [~pallavi.rao] Can you please provide the more details, how using Oozie JMS approach will help here. Also please specify how existing Falcon JMS will be used, if Oozie JMS invoke when "isNotificationEnabled" become true. > 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: FALCON-1231.patch, 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)