[
https://issues.apache.org/jira/browse/OOZIE-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038685#comment-14038685
]
Shwetha G S commented on OOZIE-1532:
------------------------------------
Even we don't use PurgeService and just delete old workflows and coord actions.
The problem with that is sometimes, you find coord action that you want to
debug and but workflow is missing or workflow action is missing. Instead,
PurgeService tries to address it by deleting only the related db rows i.e., if
bundle is deleted, delete all related coords, coord actions, workflows and
workflow actions so that all oozie entities are consistent.
In purge service, processWorkflows() takes care of independent workflows,
purgeCoordActions() takes care of independent completed coords,
processBundles() takes care completed bundles. The new addition with this patch
processCoordActions() should take of old coord actions of running coordinator
(should delete coord actions, related workflows and workflow actions)
> 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)
