[
https://issues.apache.org/jira/browse/YARN-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642286#comment-13642286
]
Andrew Ferguson commented on YARN-326:
--------------------------------------
hi Sandy,
I'm wondering if you want minimum and maximum shares to actually be fractions
of the cluster, rather than resource vectors? that would fit more with the
"fairness" aspect of the FairScheduler, but it's completely a design decision.
for example, what happens if the sum of the minimum shares for each queue
exceeds the size of the cluster? (or the size of the cluster during a failure?)
or, if my queue has been given a minimum share of (2 CPU, 240 GB RAM) --
because I was originally using tasks with high-memory, what happens if I decide
to switch to using tasks with high-CPU and low-memory? I think a minimum share
of "1/8" might make more sense since it would allow the queue's users to
request the resources as they see fit.
anyway, just a thought.
cheers,
Andrew
> Add multi-resource scheduling to the fair scheduler
> ---------------------------------------------------
>
> Key: YARN-326
> URL: https://issues.apache.org/jira/browse/YARN-326
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: scheduler
> Affects Versions: 2.0.2-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Attachments: FairSchedulerDRFDesignDoc.pdf, YARN-326.patch
>
>
> With YARN-2 in, the capacity scheduler has the ability to schedule based on
> multiple resources, using dominant resource fairness. The fair scheduler
> should be able to do multiple resource scheduling as well, also using
> dominant resource fairness.
> More details to come on how the corner cases with fair scheduler configs such
> as min and max resources will be handled.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
