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 45019177BA for ; Wed, 9 Sep 2015 13:58:47 +0000 (UTC) Received: (qmail 27881 invoked by uid 500); 9 Sep 2015 13:58:47 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 27818 invoked by uid 500); 9 Sep 2015 13:58:47 -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 27659 invoked by uid 99); 9 Sep 2015 13:58:47 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Sep 2015 13:58:47 +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 A03931A09FE for ; Wed, 9 Sep 2015 13:58:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.774 X-Spam-Level: * X-Spam-Status: No, score=1.774 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, RP_MATCHES_RCVD=-0.006] 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 36SJgBAw7iSo for ; Wed, 9 Sep 2015 13:58:46 +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 E17C120103 for ; Wed, 9 Sep 2015 13:58:45 +0000 (UTC) Received: (qmail 27574 invoked by uid 99); 9 Sep 2015 13:58:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Sep 2015 13:58:45 +0000 Date: Wed, 9 Sep 2015 13:58:45 +0000 (UTC) From: "Peeyush Bishnoi (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FALCON-1433) Falcon retry instance do not proceed on failure 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-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736885#comment-14736885 ] Peeyush Bishnoi commented on FALCON-1433: ----------------------------------------- On debugging, I found that this issue is happening because by default parameter "oozie.wf.rerun.failnodes" is getting set to "true". Due to this, when rerun happen for failed Falcon instance, only failed workflow user action invoke and corresponding post-processing action does not invoke. As post-processing does not invoke, rerun service will not launch (in case of failure) and hence further retry attempts will not happen. So to ensure that all retry attempts should happen if workflow user action failed, we need to set the "oozie.wf.rerun.failnodes" to "false". Thoughts please. > Falcon retry instance do not proceed on failure > ----------------------------------------------- > > Key: FALCON-1433 > URL: https://issues.apache.org/jira/browse/FALCON-1433 > Project: Falcon > Issue Type: Bug > Components: rerun > Reporter: Peeyush Bishnoi > Assignee: Peeyush Bishnoi > Priority: Critical > Fix For: trunk > > > When retry is specified in Falcon entity with number of attempts more than 1 and if workflow failed, on retrying Falcon instance workflow (if action fail again) seems like stuck and further attempts also does not get retry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)