You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Maxim Khutornenko (JIRA)" <ji...@apache.org> on 2015/02/24 02:22:12 UTC
[jira] [Commented] (AURORA-1134) Quota checks are inaccurate for
cron schedule updates
[ https://issues.apache.org/jira/browse/AURORA-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334209#comment-14334209 ]
Maxim Khutornenko commented on AURORA-1134:
-------------------------------------------
Relevant RBs:
https://reviews.apache.org/r/31235/
https://reviews.apache.org/r/31241
> Quota checks are inaccurate for cron schedule updates
> -----------------------------------------------------
>
> Key: AURORA-1134
> URL: https://issues.apache.org/jira/browse/AURORA-1134
> Project: Aurora
> Issue Type: Bug
> Components: Scheduler
> Reporter: Maxim Khutornenko
> Assignee: Maxim Khutornenko
>
> Cron job resources are treated as an addition rather than a replacement during cron schedule update. This leads to double counting of the updated schedule, which creates a problem when a role is hovering around its quota limit. We need a new API in the QuotaManager to properly handle this case. Something like {{QuotaManager.checkCronUpdate()}} that would properly subtract existing cron schedule consumption before comparing against quota.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)