[
https://issues.apache.org/jira/browse/AURORA-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Khutornenko updated AURORA-1431:
--------------------------------------
Sprint: Twitter Aurora Q2'15 Sprint 9
> 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
>
> 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)
