[YARN-853] maximum-am-resource-percent doesn't work after refreshQueues command

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.0-beta, 2.0.5-alpha, 3.0.0-alpha1
• Fix Version/s: 2.1.0-beta, 0.23.11
• Component/s: capacityscheduler
• Target Version/s: 2.1.0-beta
• Hadoop Flags: Reviewed
• Assignee: Devaraj Kavali
• Reporter: Devaraj Kavali
• Created: 19/Jun/13 13:29
• Updated: 12/May/16 18:29
• Resolved: 22/Jul/13 23:51

Description

If we update yarn.scheduler.capacity.maximum-am-resource-percent / yarn.scheduler.capacity.<queue-path>.maximum-am-resource-percent configuration and then do the refreshNodes, it uses the new config value to calculate Max Active Applications and Max Active Application Per User. If we add new node after issuing 'rmadmin -refreshQueues' command, it uses the old maximum-am-resource-percent config value to calculate Max Active Applications and Max Active Application Per User.