You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Zameer Manji (JIRA)" <ji...@apache.org> on 2015/11/10 19:00:16 UTC
[jira] [Updated] (AURORA-1431) Slave reservation is too restrictive
[ https://issues.apache.org/jira/browse/AURORA-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zameer Manji updated AURORA-1431:
---------------------------------
Fix Version/s: 0.10.0
> Slave reservation is too restrictive
> ------------------------------------
>
> Key: AURORA-1431
> URL: https://issues.apache.org/jira/browse/AURORA-1431
> Project: Aurora
> Issue Type: Bug
> Components: Scheduler
> Reporter: Maxim Khutornenko
> Assignee: Maxim Khutornenko
> Priority: Blocker
> Fix For: 0.10.0
>
>
> This is a regression introduced in https://reviews.apache.org/r/37001/. The updated TaskAssigner logic looks for an exclusive task->slave match any time a slave reservation is present. Any time scheduling fails and a slave reservation is created by the preemptor a task group gets effectively locked into the reserved slave. Given that reverse slave->task relationship is no longer enforced, a reserved slave could be taken by some other task thus slowing down scheduling progress.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)