You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "daemon (JIRA)" <ji...@apache.org> on 2017/07/09 05:21:00 UTC
[jira] [Comment Edited] (YARN-6769) Put the no demand queue after
the most in FairSharePolicy#compare
[ https://issues.apache.org/jira/browse/YARN-6769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079453#comment-16079453 ]
daemon edited comment on YARN-6769 at 7/9/17 5:20 AM:
------------------------------------------------------
[~yufei] Thanks yufei. I have already upload my patch file, what is the next I should do?
was (Author: daemon):
[~yufei] Thanks yufei. I have already upload my patch file, what is the next I should do?
> Put the no demand queue after the most in FairSharePolicy#compare
> -----------------------------------------------------------------
>
> Key: YARN-6769
> URL: https://issues.apache.org/jira/browse/YARN-6769
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler
> Affects Versions: 2.7.2
> Reporter: daemon
> Assignee: daemon
> Priority: Minor
> Fix For: 2.9.0
>
> Attachments: YARN-6769.001.patch
>
>
> When use fairsheduler as RM scheduler, before assign container we will sort all queues or applications.
> We will use FairSharePolicy#compare as the comparator, but the comparator is not so perfect.
> It have a problem as blow:
> 1. when a queue use resource over minShare(minResources), it will put behind the queue whose demand is zeor.
> so it will greater opportunity to get the resource although it do not want. It will waste schedule time when assign container
> to queue or application.
> I have fix it, and I will upload the patch to the jira.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org