aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jake Farrell (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AURORA-416) Scheduling rate limiter is not used
Date Fri, 16 May 2014 11:15:16 GMT

     [ https://issues.apache.org/jira/browse/AURORA-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jake Farrell updated AURORA-416:
--------------------------------

    Fix Version/s:     (was: 0.6.0)
                   0.5.0

> Scheduling rate limiter is not used
> -----------------------------------
>
>                 Key: AURORA-416
>                 URL: https://issues.apache.org/jira/browse/AURORA-416
>             Project: Aurora
>          Issue Type: Bug
>          Components: Scheduler
>            Reporter: Bill Farner
>            Priority: Critical
>              Labels: newbie
>             Fix For: 0.5.0
>
>
> {{TaskGroups}} receives a {{RateLimiter}}, but it is currently unused.  This means that
scheduling rate is unbounded.
> This is a regression introduced in https://git-wip-us.apache.org/repos/asf?p=incubator-aurora.git;a=commit;h=f73e29b3196f13e37d31c8e02dd17628edb548e0
> Specifically, this is no longer used:
> {noformat}
>     final TaskScheduler ratelLimitedScheduler = new TaskScheduler() {
>       @Override
>       public boolean schedule(String taskId) {
>         rateLimiter.acquire();
>         return taskScheduler.schedule(taskId);
>       }
>     };
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message