[
https://issues.apache.org/jira/browse/AURORA-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167035#comment-14167035
]
Maxim Khutornenko commented on AURORA-825:
------------------------------------------
The problem with accounting for staggered setup is the total lack of task
runtime duration prediction/guarantees. I think we should assume the worst case
of a task never ending its execution. This is certainly possible with
KILL_EXISTING policy and even more so with RUN_OVERLAP.
Ideally, it would be great to support a user configurable hard stop for a cron
task (e.g. KILL_IF_NOT_FINISHED_AFTER_MS) that we could use to more accurately
count cron consumption.
> Cron tasks don't check quota when launched
> ------------------------------------------
>
> Key: AURORA-825
> URL: https://issues.apache.org/jira/browse/AURORA-825
> Project: Aurora
> Issue Type: Task
> Components: Scheduler
> Reporter: Maxim Khutornenko
>
> We don't check production quota when a cron task is launched by the
> CronJobManager. This leaves a potential to temporarily exceed allocated quota
> if prod consumption grew close to the limit _after_ a cron job was created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
