[
https://issues.apache.org/jira/browse/AURORA-825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167003#comment-14167003
]
Maxim Khutornenko commented on AURORA-825:
------------------------------------------
How about following the same approach that we implemented for job updates?
Production cron schedules could be aggregated at the point of quota validation
during create/schedule to disallow anything that would exceed the limits. This
way the role consumption is always kept compliant wrt its quota without the
adversity of blocking scheduled runs.
> 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)
