[jira] [Created] (YARN-4399) FairScheduler allocated container should resetSchedulingOpportunities count of its priority

["Lin Yiqun (JIRA)" <ji...@apache.org>]

Lin Yiqun created YARN-4399:
-------------------------------

             Summary: FairScheduler allocated container should resetSchedulingOpportunities count of its priority
                 Key: YARN-4399
                 URL: https://issues.apache.org/jira/browse/YARN-4399
             Project: Hadoop YARN
          Issue Type: Bug
          Components: scheduler
    Affects Versions: 2.7.1
            Reporter: Lin Yiqun
            Assignee: Lin Yiqun


There is a bug on fairScheduler allocating containers when you configurate the locality configs.When you attempt to assigned a container,it will invoke {{FSAppAttempt#addSchedulingOpportunity}} whenever it can be assigned successfully or not. And if you configurate the yarn.scheduler.fair.locality.threshold.node and yarn.scheduler.fair.locality.threshold.rack, the schedulingOpportunity value will influence the locality of containers.Because if one container is assigned successfully and its  priority schedulingOpportunity count will be increased, and second container will be increased again.This will may be let their priority of allowedLocality degrade. And this will let this container dealt by rackRequest. So I think in fairScheduler allocating container, if the previous container was dealt, its priority of schedulerCount should be reset to 0, and don't let its value influence container's allocating in next iteration and this will increased the locality of containers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)