[
https://issues.apache.org/jira/browse/OOZIE-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038539#comment-14038539
]
Shwetha G S commented on OOZIE-1532:
------------------------------------
@NamedQuery(name = "GET_COMPLETED_COORD_WORKFLOWS_OLDER_THAN", query = "select
w.id, w.parentId from WorkflowJobBean w where w.endTimestamp < :endTime and
w.parentId like '%C@%'")
This query is expensive. Instead, can we get coord action id/workflow id from
COORD_ACTIONS first. Also this should be looking at just running coords
> 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)
