[
https://issues.apache.org/jira/browse/OOZIE-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026160#comment-14026160
]
Shwetha G S commented on OOZIE-1532:
------------------------------------
Purge configuration is at oozie server level and oozie users(owners of coords)
will not be aware of when exactly the purge service runs(or even enabled) or
how much is purged. To be consistent, the action get should always return
actions relative to coord beginning and not relative to the actions in db
> 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
>
>
> 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)
