falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajay Yadava (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1492) Change default execution order in oozie's retention coord to LAST_ONLY
Date Sun, 27 Sep 2015 19:37:04 GMT

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

Ajay Yadava commented on FALCON-1492:


Completely agree with you, in fact [~sriksun] and I had this exact same discussion a few days
back. I have already uploaded a patch for lifecycle (FALCON-965), we are targeting 0.8 release
which is planned for mid October. If you want you can go ahead with this JIRA, in any case
I will add this behavior to the lifecycle. 

> Change default execution order in oozie's retention coord to LAST_ONLY
> ----------------------------------------------------------------------
>                 Key: FALCON-1492
>                 URL: https://issues.apache.org/jira/browse/FALCON-1492
>             Project: Falcon
>          Issue Type: Bug
>          Components: oozie, retention
>    Affects Versions: 0.7
>            Reporter: Shaik Idris Ali
>            Assignee: Shaik Idris Ali
>            Priority: Minor
>             Fix For: 0.8
> Currently in falcon's retention coord the default execution order is not LAST_ONLY which
oozie supports anyway.
> Ideally in case of backlogs, (happens when cluster is constrained) the cluster unnecessary
tries to clear the backloged workflows even for retention, which is not required as it is
a kind of singleton process.
> [~pallavi.rao], if we are planning to release the new life-cycle management anytime soon
then we can close this issue.

This message was sent by Atlassian JIRA

View raw message