[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-10.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, > OOZIE-2041-05.patch, OOZIE-2041-06.patch, OOZIE-2041-07.patch, > OOZIE-2041-08.patch, OOZIE-2041-09.patch, OOZIE-2041-10.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.15#6346)
[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-09.patch Rebase last (08) 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, > OOZIE-2041-05.patch, OOZIE-2041-06.patch, OOZIE-2041-07.patch, > OOZIE-2041-08.patch, OOZIE-2041-09.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.15#6346)
[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-07.patch Thanks [~asasvari] for the feedback. bq. Typo in the documentation: "bundle records (bundle=6) older than 7 days." I am not able to catch the typo in here. Can you please help by pointing out. bq. In {{OozieClient}}, you could add some parameter validation like this The validation is added into the {{BaseAdminServlet}} so that it can work informally with CLI and REST. I think it will be redundant to add in the {{OozieClient}}. Do let me know your thoughts. You mentioned about, playing around with CLI, If there is anything do post it here. Thanks. > 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, > OOZIE-2041-05.patch, OOZIE-2041-06.patch, OOZIE-2041-07.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)
[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-06.patch [~gezapeti], [~andras.piros] and [~asasvari] Thanks for the feedback. Please have a look into the updated patch. Thanks. [~gezapeti] There is no change into {{setOozieMode}}, just a refactoring as we got one more 'admin' command in the {{doPut}}. > 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, > OOZIE-2041-05.patch, OOZIE-2041-06.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)
[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-05.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, > OOZIE-2041-05.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)
[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)
[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: -- Fix Version/s: 5.0.0 > 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 > > > 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)
[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-03.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 > Attachments: OOZIE-2041-00.patch, OOZIE-2041-01.patch, > OOZIE-2041-02.patch, OOZIE-2041-03.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)
[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-02.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 > Attachments: OOZIE-2041-00.patch, OOZIE-2041-01.patch, > OOZIE-2041-02.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)
[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-01.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 > Attachments: OOZIE-2041-00.patch, OOZIE-2041-01.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)
[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-00.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 > Attachments: OOZIE-2041-00.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)