You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Abhishek Bafna (JIRA)" <ji...@apache.org> on 2016/12/19 13:26:58 UTC

[jira] [Updated] (OOZIE-2041) Add an admin command to run the PurgeXCommand

     [ https://issues.apache.org/jira/browse/OOZIE-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Abhishek Bafna updated OOZIE-2041:
----------------------------------
    Attachment: OOZIE-2041-04.patch

Rebase patch.

> Add an admin command to run the PurgeXCommand
> ---------------------------------------------
>
>                 Key: OOZIE-2041
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2041
>             Project: Oozie
>          Issue Type: New Feature
>          Components: core
>    Affects Versions: trunk
>            Reporter: Robert Kanter
>            Assignee: Abhishek Bafna
>             Fix For: 5.0.0
>
>         Attachments: OOZIE-2041-00.patch, OOZIE-2041-01.patch, OOZIE-2041-02.patch, OOZIE-2041-03.patch, OOZIE-2041-04.patch
>
>
> Some users may find it useful to be able to run the PurgeXCommand on-demand.  We can add a new admin command to run this.  e.g.
> {noformat}
> oozie admin -purge
> {noformat}
> With no args, it can use the "older than" values from oozie-site, but we could have it take some arguments to override those for the command.
> Another thing to worry about is making sure that we don't run this if either it's already running (i.e. the user sent it twice) or if the scheduled PurgeService is already running it.  On top of that, we may need extra consideration for HA setups where we currently only run it on the leader.  
> We should probably also have a to not schedule the PurgeService in ooize-site for users who only want to run it manually.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)