[
https://issues.apache.org/jira/browse/AURORA-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167305#comment-14167305
]
Kevin Sweeney commented on AURORA-825:
--------------------------------------
I think the update approach is reasonable - account the greater of either the
resources the dormant cron job *would* use and the running tasks created by it.
That way you can replaceCronTemplate to a lower resource usage and still be
charged for the running tasks.
Note that RUN_OVERLAP was removed (AURORA-38) in part because it's not easily
accountable.
> 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)
