[
https://issues.apache.org/jira/browse/AURORA-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Farner updated AURORA-878:
-------------------------------
Description:
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.
was:
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
persisting 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.
Summary: Cache Host Attributes along Offer (was: Persist Host
Attributes along Offer)
> 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
>
> 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)
