[YARN-7619] Max AM Resource value in Capacity Scheduler UI has to be refreshed for every user

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9.0, 3.0.0-beta1, 2.8.2, 3.1.0
• Fix Version/s: 3.1.0, 2.10.0, 2.9.1, 3.0.1, 2.8.4
• Component/s: capacity scheduler, yarn
• Hadoop Flags: Reviewed
• Assignee: Eric Payne
• Reporter: Eric Payne
• Created: 06/Dec/17 16:50
• Updated: 14/Oct/19 15:38
• Resolved: 05/Jan/18 09:31

Description

YARN-7245 addressed the problem that the Max AM Resource in the capacity scheduler UI used to contain the queue-level AM limit instead of the user-level AM limit. It fixed this by using the user-specific AM limit that is calculated in LeafQueue#activateApplications, stored in each user's LeafQueue#User object, and retrieved via UserInfo#getResourceUsageInfo.

The problem is that this user-specific AM limit depends on the activity of other users and other applications in a queue, and it is only calculated and updated when a user's application is activated. So, when CapacitySchedulerPage retrieves the user-specific AM limit, it is a stale value unless an application was recently activated for a particular user.

Issue Links

• causes: YARN-8730 TestRMWebServiceAppsNodelabel#testAppsRunning fails