Bill Farner created AURORA-137:
----------------------------------
Summary: Save host attributes only when a task is being scheduled
Key: AURORA-137
URL: https://issues.apache.org/jira/browse/AURORA-137
Project: Aurora
Issue Type: Story
Components: Scheduler
Reporter: Bill Farner
The scheduler currently aggressively saves host attributes when handling
{{resourceOffers}}, however it seems tractable for this to only happen when a
task is actually scheduled. Context: the scheduler stores host attributes to
satisfy scheduling constraints (like host/rack diversity). Doing this would
allow us to avoid waiting for the storage write lock, and handle
{{resourceOffers}} in a more deterministic time frame.
One caveat with this approach is that the Offer would need to be plumbed into
{{SchedulingFilterImpl}} in a way so as to ensure that the attributes are
available for the offer being inspected. In other words, we need to avoid the
chicken and egg of trying to read the attributes for a host when this is the
first offer ever received for it.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
