[AMBARI-18967] Use max-AM percentage for a queue selected, instead of reading from top level common.

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.4.1
• Fix Version/s: 2.5.0
• Component/s: ambari-server
• Assignee: Swapan Shridhar
• Reporter: Swapan Shridhar
• Due: 23/Nov/16
• Created: 23/Nov/16 00:31
• Updated: 27/Jan/17 20:16
• Resolved: 27/Jan/17 20:16

Description

Current:

• We are reading the top level max-AM percent value for non 'llap' named queue at root level.
  Eg: yarn.scheduler.capacity.maximum-am-resource-percent=1

Required:

AM Percent value should be read as:

• Fetch the 'AM Percent' value for queue in consideration, if exists, else
• Return default value as 0.1.

Eg:
Say queue in consideration is named: 'xyz' and is at depth 3. Thus, the expected 'key' config to be read is :

yarn.scheduler.capacity.root.abc.xyz.maximum-am-resource-percent=<some value>

Issue Links

• is related to: AMBARI-18901 LLAP integration enhancements
• links to: Reviewboard Link