[
https://issues.apache.org/jira/browse/AURORA-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619277#comment-14619277
]
Bill Farner commented on AURORA-1384:
-------------------------------------
The thing that always makes me pause when considering different scheduling
algorithms is expectations around convergence towards the target distribution.
Augmenting the way offers are selected is one part of the story; but in a
cluster with little churn, i imagine it would be desirable for tasks to be
retroactively moved to fit the desired arrangement.
Just something to consider, i don't necessary think this is required for an
improvement over what we have today. Thanks for raising the discussion!
> Provide alternate policies for offer assignment to tasks
> --------------------------------------------------------
>
> Key: AURORA-1384
> URL: https://issues.apache.org/jira/browse/AURORA-1384
> Project: Aurora
> Issue Type: Story
> Components: Scheduler
> Affects Versions: 0.8.0
> Reporter: Anindya Sinha
>
> Currently, offers are arranged in a list. When new tasks need to be assigned
> an offer, the first offer from the list that matches the task constraints is
> assigned which over time may result in a non even distribution of tasks on
> slaves in the cluster.
> In addition to existing algorithm ("first-fit"), we can support alternate
> algorithms as follows:
> i) bin-packed: Offer is assigned to a task based on a bin packed algorithm
> which ensures a specific offer is used up to the maximum possible with
> respect to resources (cpu) before moving to an alternate offer.
> ii) even-distribution: Offer is assigned to ensure even distribution of load
> on each slave on the cluster based on resources (cpu).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
