[
https://issues.apache.org/jira/browse/FALCON-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2116:
------------------------------------
Fix Version/s: 0.11
> 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, 0.11
>
>
> 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 suspended.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
