[
https://issues.apache.org/jira/browse/OOZIE-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038486#comment-14038486
]
Purshotam Shah commented on OOZIE-1532:
---------------------------------------
{quote}
And the ticket is about removing workflow jobs of long running coordinator jobs.
{quote}
{code}
@NamedQuery(name = "DELETE_ACTIONS_FOR_LONG_RUNNING_COORDINATOR", query =
"delete from CoordinatorActionBean a where a.id = :actionId"),
{code}
You are deleting coord actions ( only those action which has launched WF),
which is like half done. We might have to create a different JIRA to delete
TIMEDOUT actions. Why not to do in one go. We can use lastModifiedTimestamp.
Coord actions which has not being modified in last 30 days can be purged.
> 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)
