[
https://issues.apache.org/jira/browse/AURORA-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986192#comment-14986192
]
Bill Farner commented on AURORA-1528:
-------------------------------------
With this use case as an example, my major concern is that we could give the
user a false sense of security that we are protecting them from corrupting
(their external) data during an operation like a schema migration.
Given that risk, disclaimers/warnings, and knobs we would need to include to
enable this, i don't think it's something we should pursue.
> 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)
