[
https://issues.apache.org/jira/browse/AURORA-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985946#comment-14985946
]
Joshua Cohen commented on AURORA-1528:
--------------------------------------
[~dabaitu] Unfortunately it's a bit more complex than just having the quartz
scheduler pause/resume the job. The fact that the cron job is snoozed would
need to be written to Aurora's storage so that in the event of a failover that
snooze is respected by the new leader.
[~wfarner] This still seems like nice-to-have functionality to me, though I
admit the use case is probably fairly limited. It's a question of whether the
complexity to maintain this outweighs the complexity of requiring people to
manage this outside of Aurora.
> New snooze feature for cron jobs
> --------------------------------
>
> Key: AURORA-1528
> URL: https://issues.apache.org/jira/browse/AURORA-1528
> Project: Aurora
> Issue Type: Story
> Components: Scheduler
> Reporter: Thomas Sun
> Assignee: Thomas Sun
> Priority: Minor
>
> something that would fulfill my need would be in the next
> d:h:m:s(days:hours:minutes:seconds) from NOW,
> do not run(or skip running) the job even though it may be scheduled to run
> for x times within that time range.
> if a job is scheduled to run at T0, T6, T12, T18 UTC everyday, and I did a
> snooze 0:8:0:0 for this job at UTC T16, then the next 2 runs(T18 today and T0
> tomorrow) of the job should be skipped.
> another useful interface for me would be snooze x -> x is the number of runs
> from NOW to skip.
> Design:
> https://docs.google.com/document/d/1NEMb9Qbc9T9ZBlOifkRjB2OYGnO_pNURNQcsSLXArSk/edit
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
