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 Wed, 17 Aug 2016 04:01:20 GMT

    [ https://issues.apache.org/jira/browse/FALCON-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15423840#comment-15423840

ASF GitHub Bot commented on FALCON-2116:

Github user asfgit closed the pull request at:


> 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
>             Fix For: trunk
> 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