aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zameer Manji (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (AURORA-878) Cache Host Attributes along Offer
Date Fri, 24 Oct 2014 23:14:33 GMT

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

Zameer Manji reassigned AURORA-878:
-----------------------------------

    Assignee: Zameer Manji

> Cache Host Attributes along Offer
> ---------------------------------
>
>                 Key: AURORA-878
>                 URL: https://issues.apache.org/jira/browse/AURORA-878
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler
>            Reporter: Zameer Manji
>            Assignee: Zameer Manji
>
> At a large production cluster [~wfarner] and I have noticed that a lot of time is spent
reading from the attribute store during scheduling. This is because when scheduling tasks
we need to check the attributes of the slave before accepting an offer. We do this to compute
diversity constraints.
> We can prevent frequent reading from the attribute store in this process by caching attributes
alongside the offers. That way when we get an offer from a slave we can check the diversity
constraints without reading from the AttributeStore.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message