[YARN-4399] FairScheduler allocated container should resetSchedulingOpportunities count of its priority

• Type: Bug
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.7.1
• Component/s: fairscheduler
• Labels: oct16-hard
• Assignee: Yiqun Lin
• Reporter: Yiqun Lin
• Created: 30/Nov/15 14:34
• Updated: 27/Oct/16 21:39

Description

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.

Issue Links

• is related to: YARN-4440 FSAppAttempt#getAllowedLocalityLevelByTime should init the lastScheduler time
• is related to: YARN-4396 Log the trace information on FSAppAttempt#assignContainer