Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A1FC6200B63 for ; Mon, 15 Aug 2016 18:53:25 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A07E7160AB8; Mon, 15 Aug 2016 16:53:25 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E8A34160A8A for ; Mon, 15 Aug 2016 18:53:24 +0200 (CEST) Received: (qmail 87756 invoked by uid 500); 15 Aug 2016 16:53:24 -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 87745 invoked by uid 99); 15 Aug 2016 16:53:24 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Aug 2016 16:53:24 +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 9E2C1188593 for ; Mon, 15 Aug 2016 16:53:23 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.396 X-Spam-Level: X-Spam-Status: No, score=-4.396 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, KAM_LOTSOFHASH=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id WWma5qSZ6Jlc for ; Mon, 15 Aug 2016 16:53:21 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with SMTP id 51C1D5F366 for ; Mon, 15 Aug 2016 16:53:21 +0000 (UTC) Received: (qmail 87612 invoked by uid 99); 15 Aug 2016 16:53:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Aug 2016 16:53:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 82FD02C02A4 for ; Mon, 15 Aug 2016 16:53:20 +0000 (UTC) Date: Mon, 15 Aug 2016 16:53:20 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FALCON-2116) Queue defined in is not getting used in actual retention job MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 15 Aug 2016 16:53:25 -0000 [ https://issues.apache.org/jira/browse/FALCON-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421255#comment-15421255 ] ASF GitHub Bot commented on FALCON-2116: ---------------------------------------- GitHub user sandeepSamudrala opened a pull request: https://github.com/apache/falcon/pull/266 FALCON-2116 Queue defined in is not getting used in actual retention job You can merge this pull request into a Git repository by running: $ git pull https://github.com/sandeepSamudrala/falcon FALCON-2116 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/falcon/pull/266.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #266 ---- commit 9e68a578328e284dcdf845ce32a0c48ac8dba36c Author: sandeep Date: 2016-07-25T06:36:59Z FALCON-298. Feed update with replication delay creates holes commit a94d4fe07f0da2606fc1c9009ba9a2d62643b728 Author: sandeep Date: 2016-08-05T10:57:34Z rebasing from master commit 271318b9cadde6f4341d3c02e9e71838db490023 Author: sandeep Date: 2016-08-05T10:58:13Z FALCON-2097. Adding UT to the new method for getting next instance time with Delay. commit 1a4dcd234e8fe849ad415e8c9681a7d00395a107 Author: sandeep Date: 2016-08-05T11:03:55Z rebased and resolved the conflicts from master commit c06556623e87cbc52f6b01d44cc420bbb92c72e9 Author: sandeep Date: 2016-08-05T11:05:08Z reverting last line changes made commit 1bb8d3c72a97835b88320ce482c5f472e00fb7cd Author: sandeep Date: 2016-08-09T06:05:15Z Merge branch 'master' of https://github.com/apache/falcon commit d6dc8bfaa6811fe3a97f1223fd962ab8fa083b47 Author: sandeep Date: 2016-08-14T08:16:50Z Merge branch 'master' of https://github.com/apache/falcon commit a23fe905344f886cc3d58464d90e889a1e205783 Author: sandeep Date: 2016-08-15T16:51:59Z FALCON-2116 Queue defined in is not getting used in actual retention job ---- > Queue defined in is not getting used in actual retention job > ------------------------------------------------------------------------------ > > Key: FALCON-2116 > URL: https://issues.apache.org/jira/browse/FALCON-2116 > Project: Falcon > Issue Type: Bug > Reporter: sandeep samudrala > Assignee: sandeep samudrala > > Following feed definition segment is not working properly, Both replication and retention jobs are running in "m10n" queue and queue from retention-stage is not getting picked up: > {noformat} > > > > > > > hours(1) > default > NORMAL > > > > > > {noformat} > Here we have a feed which replicates data from local to global cluster. We have queue "m10n" in global, but not in local colos. So we have specified "default" queue for retention jobs and "m10n" for replication jobs. > But both are getting "m10n" queue. Due to which retention jobs in local colos are getting suspended. -- This message was sent by Atlassian JIRA (v6.3.4#6332)