[
https://issues.apache.org/jira/browse/AMBARI-18967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15689974#comment-15689974
]
Hadoop QA commented on AMBARI-18967:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12840170/AMBARI-18967.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9373//console
This message is automatically generated.
> Use max-AM percentage for a queue selected, instead of reading from top level
> common.
> -------------------------------------------------------------------------------------
>
> Key: AMBARI-18967
> URL: https://issues.apache.org/jira/browse/AMBARI-18967
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.1
> Reporter: Swapan Shridhar
> Assignee: Swapan Shridhar
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18967.patch
>
>
> *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 :
> {noformat}
> yarn.scheduler.capacity.root.abc.xyz.maximum-am-resource-percent=<some value>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
