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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: trunk, 0.11
• Component/s: retention
• Assignee: sandeep samudrala
• Reporter: sandeep samudrala
• Created: 15/Aug/16 15:43
• Updated: 23/Oct/17 04:57
• Resolved: 17/Aug/16 04:00

Description

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:

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

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.

Issue Links

• links to: GitHub Pull Request #266