[
https://issues.apache.org/jira/browse/OOZIE-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038555#comment-14038555
]
Purshotam Shah commented on OOZIE-1532:
---------------------------------------
[~shwethags] Why do we want to purge only those action which has submitted WF.
We need to think of generic usage case, not an specific case.
We don't use purge script at Yahoo, we have DB script which purges all WF older
than 4 week, all WF_action older than 3 week, all coord action older than 5
weeks.
According to me
1. purging of WF/WF_action should not be based on parentID.
GET_COMPLETED_WORKFLOWS_WITH_NO_PARENT_OLDER_THAN, should be
GET_COMPLETED_WORKFLOWS_OLDER_THAN. This will even take care of long running
jobs.
2. Purging of coord action should not be based on WF.parentID. We should purge
all coord action whose lastmodifieddate < (conf).
> Purging should remove completed children job for long running coordinator jobs
> ------------------------------------------------------------------------------
>
> Key: OOZIE-1532
> URL: https://issues.apache.org/jira/browse/OOZIE-1532
> Project: Oozie
> Issue Type: New Feature
> Reporter: Srikanth Sundarrajan
> Assignee: Bowen Zhang
> Attachments: oozie-1532.patch, oozie-1532.patch, oozie-1532.patch
>
>
> Specifically, this is for long running coordinator jobs with high frequency.
> all child workflows are never purged as the coord job is still running.
> Oozie server configuration that indicates how many coordinator actions
> frequency ticks to keep. By doing this it would be possible to purge running
> coord jobs. By default this would not be enabled and the current logic would
> remain.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
