[
https://issues.apache.org/jira/browse/OOZIE-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039173#comment-14039173
]
Bowen Zhang commented on OOZIE-1532:
------------------------------------
[~puru], I will go with what [~shwethags] says. This ticket is not meant to
completely overhaul or refactor purgeServices. We should keep existing behavior
as much as possible. And even my patch needs to be turned on in the conf to
work. Without turning on in the conf, everything is the same as before.
[~shwethags], {quote} This query is expensive. Instead, can we get coord action
id/workflow id from COORD_ACTIONS first. {quote}. You won't get any wf_id from
COORD_ACTIONS and COORD_ACTIONS alone have no end_time. So, I think the query
is fine.
> 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)
