[ 
https://issues.apache.org/jira/browse/AMBARI-16921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304327#comment-15304327
 ] 

Hadoop QA commented on AMBARI-16921:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12806605/AMBARI-16921.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7021//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7021//console

This message is automatically generated.

> Yarn minimum container size calculation problem in stack advisor
> ----------------------------------------------------------------
>
>                 Key: AMBARI-16921
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16921
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Daniel Gergely
>            Assignee: Daniel Gergely
>            Priority: Blocker
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-16921.patch
>
>
> Stack advisor gets yarn minimum container size property from only the 
> "services" input, but does not take into account the already calculated 
> configurations.
> As a result memory size for hive interactive server is not correct, so it 
> doesn't start.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to