falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-2116) Queue defined in <retention-stage> is not getting used in actual retention job
Date Mon, 15 Aug 2016 16:53:20 GMT

    [ 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:


    FALCON-2116 Queue defined in <retention-stage> is not getting used in actual retention


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:


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 <sandysmdl@gmail.com>
Date:   2016-07-25T06:36:59Z

    FALCON-298. Feed update with replication delay creates holes

commit a94d4fe07f0da2606fc1c9009ba9a2d62643b728
Author: sandeep <sandysmdl@gmail.com>
Date:   2016-08-05T10:57:34Z

    rebasing from master

commit 271318b9cadde6f4341d3c02e9e71838db490023
Author: sandeep <sandysmdl@gmail.com>
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 <sandysmdl@gmail.com>
Date:   2016-08-05T11:03:55Z

    rebased and resolved the conflicts from master

commit c06556623e87cbc52f6b01d44cc420bbb92c72e9
Author: sandeep <sandysmdl@gmail.com>
Date:   2016-08-05T11:05:08Z

    reverting last line changes made

commit 1bb8d3c72a97835b88320ce482c5f472e00fb7cd
Author: sandeep <sandysmdl@gmail.com>
Date:   2016-08-09T06:05:15Z

    Merge branch 'master' of https://github.com/apache/falcon

commit d6dc8bfaa6811fe3a97f1223fd962ab8fa083b47
Author: sandeep <sandysmdl@gmail.com>
Date:   2016-08-14T08:16:50Z

    Merge branch 'master' of https://github.com/apache/falcon

commit a23fe905344f886cc3d58464d90e889a1e205783
Author: sandeep <sandysmdl@gmail.com>
Date:   2016-08-15T16:51:59Z

    FALCON-2116 Queue defined in <retention-stage> is not getting used in actual retention


> Queue defined in <retention-stage> 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}
> <properties>
>         <property name="webhdfs" value="enabled"/>
>         <property name="queueName" value="m10n"/>
>     </properties>
>     <lifecycle>
>         <retention-stage>
>             <frequency>hours(1)</frequency>
>             <queue>default</queue>
>             <priority>NORMAL</priority>
>             <properties>
>                 <property name="retention.policy.agebaseddelete.limit" value="days(10)"/>
>             </properties>
>         </retention-stage>
>     </lifecycle>
> {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

This message was sent by Atlassian JIRA

View raw message