You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2014/11/11 19:46:34 UTC

[jira] [Commented] (OOZIE-2062) Provide alternate purging logic

    [ https://issues.apache.org/jira/browse/OOZIE-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206791#comment-14206791 ] 

Robert Kanter commented on OOZIE-2062:
--------------------------------------

{quote}Currently, purge service deletes a workflow only if all its children are complete, coord action only if the corresponding workflow and its sub-workflows are complete. Instead, provide an alternative purging logic that deleted all workflows whose end time is older than configured time, delete coord actions whose end time is older than configured time and so on. {quote}
I'm all for adding alternative purging logic behaviors, but don't we already support this with OOZIE-1532?  It's disabled by default, but if you set {{oozie.service.PurgeService.purge.old.coord.action=true}} Oozie will delete child workflows before their parent coordinator is complete.

> Provide alternate purging logic
> -------------------------------
>
>                 Key: OOZIE-2062
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2062
>             Project: Oozie
>          Issue Type: Improvement
>            Reporter: Shwetha G S
>            Assignee: Jaydeep Vishwakarma
>
> Currently, purge service deletes a workflow only if all its children are complete, coord action only if the corresponding workflow and its sub-workflows are complete. This logic is complicated and takes longer to run. Instead, provide an alternative purging logic that deleted all workflows whose end time is older than configured time, delete coord actions whose end time is older than configured time and so on. The purging logic to be used can be configured from oozie-site (by default can default to the current logic for backward compatbility)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)