[
https://issues.apache.org/jira/browse/OOZIE-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14034896#comment-14034896
]
Purshotam Shah commented on OOZIE-1532:
---------------------------------------
Purging is always configured at server level, user can't override it or disable
it.
{quote}
Currently for a running coord, the DB has all the actions(say C@0 to C@100).
Coord action get with start as 10 and len 10 returns actions C@10 to C@19.
Now assume that purging of actions for running coords is enabled and configured
to run every 2 hours and should delete the first 10 actions(min action in DB is
C@10). Without the changes to CoordJobGetActionsSubsetJPAExecutor, depending on
when the user calls coord action get, the user will get different results.
i.e., If the user makes a call before the purge service runs, the same coord
action get(with start as 11 and len 10) returns actions C@10 to C@19. After the
purge service runs, the coord action get(with start as 11 and len 10) returns
actions C@20 to C@29. This is confusing for the users and there is no way for
the users to know when the purge service runs or how oozie service is
configured. Why should the users care about oozie maintenance(thats admins
responsibility).
{quote}
Normally you will purge coord action older than few day ( may 30), so
assumption is that no body is going to look at purged coord actions.
So i believe it ok ( we can't get purge action). Most of the case user will be
interested in recent actions.
One other suggestion could be is to provide "recentLen", which will provide "n"
recent action. I believe this is what most of the user is looking for.
> 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)
