[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=15834696#comment-15834696
]
Abhishek Bafna edited comment on OOZIE-2041 at 1/23/17 3:43 PM:
Thanks [~asasvari] for looking into the patch.
For the typo, It should be {{"bundle records (bundle=7) older than 7 days."}},
which was correct in earlier patches I think.
For the validation, I will create a ValidationUtil class into oozie-client
module, oozie-core have access to it and then will reuse the same. This class
can be used in future for adding more validation checks.
Thanks.
was (Author: abhishekbafna):
Thanks [~asasvari] for looking into the patch.
For the typo, It should be {{"bundle records (bundle=6) older than 7 days."}},
which was correct in earlier patches I think.
For the validation, I will create a ValidationUtil class into oozie-client
module, oozie-core have access to it and then will reuse the same. This class
can be used in future for adding more validation checks.
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] [Comment Edited] (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:comment-tabpanel&focusedCommentId=15834705#comment-15834705
]
Peter Cseh edited comment on OOZIE-2041 at 1/23/17 3:02 PM:
I think I don't understand the documentation.
If I want to purge all my wfs, coord jobs and bundles older that 7 days, which
one of the following commands is the correct?
# {{oozie admin purge wf=7,bundle=7,coord=7 }}
# {{oozie admin purge wf=7,bundle=6,coord=7 }}
1 or 2?
was (Author: gezapeti):
I think I don't understand the documentation.
If I want to purge all my wfs, coord jobs and bundles older that 7 days, which
one of the following commands is the correct?
#{{oozie admin purge wf=7,bundle=7,coord=7 }}
#{{oozie admin purge wf=7,bundle=6,coord=7 }}
1 or 2?
> 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)
