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 B3A8618318 for ; Sun, 27 Sep 2015 19:37:05 +0000 (UTC) Received: (qmail 57267 invoked by uid 500); 27 Sep 2015 19:37:05 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 57225 invoked by uid 500); 27 Sep 2015 19:37: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 57212 invoked by uid 99); 27 Sep 2015 19:37:05 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 Sep 2015 19:37:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 00C101809CF for ; Sun, 27 Sep 2015 19:37:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id KKEXGYJvF1nt for ; Sun, 27 Sep 2015 19:37:04 +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 618F7206AE for ; Sun, 27 Sep 2015 19:37:04 +0000 (UTC) Received: (qmail 57204 invoked by uid 99); 27 Sep 2015 19:37:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 Sep 2015 19:37:04 +0000 Date: Sun, 27 Sep 2015 19:37:04 +0000 (UTC) From: "Ajay Yadava (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FALCON-1492) Change default execution order in oozie's retention coord to LAST_ONLY 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-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909861#comment-14909861 ] Ajay Yadava commented on FALCON-1492: ------------------------------------- [~shaik.idris] Completely agree with you, in fact [~sriksun] and I had this exact same discussion a few days back. I have already uploaded a patch for lifecycle (FALCON-965), we are targeting 0.8 release which is planned for mid October. If you want you can go ahead with this JIRA, in any case I will add this behavior to the lifecycle. > Change default execution order in oozie's retention coord to LAST_ONLY > ---------------------------------------------------------------------- > > Key: FALCON-1492 > URL: https://issues.apache.org/jira/browse/FALCON-1492 > Project: Falcon > Issue Type: Bug > Components: oozie, retention > Affects Versions: 0.7 > Reporter: Shaik Idris Ali > Assignee: Shaik Idris Ali > Priority: Minor > Fix For: 0.8 > > > Currently in falcon's retention coord the default execution order is not LAST_ONLY which oozie supports anyway. > Ideally in case of backlogs, (happens when cluster is constrained) the cluster unnecessary tries to clear the backloged workflows even for retention, which is not required as it is a kind of singleton process. > [~pallavi.rao], if we are planning to release the new life-cycle management anytime soon then we can close this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)