[
https://issues.apache.org/jira/browse/OOZIE-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037011#comment-14037011
]
Purshotam Shah commented on OOZIE-1532:
---------------------------------------
Its depend on how do u interpret "len". For me it's number of coord action
available. It doesn't represent action number .If user knows that coord older
than (30 days) is purged and len=10 returning 10 available is also ok.
I am ok with both approach.
I see other issue with patch. For deleting coord action you are trying to get
coord action from WF table. There are few cases where coord action will not
submit WF, like if it gets timeout. We have to delete those coord action as
well.
> 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)
