ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-19764) yarn.min.container.size is read incorrectly on first load of the Hive config page
Date Sat, 28 Jan 2017 08:34:25 GMT

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

Hadoop QA commented on AMBARI-19764:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12849801/AMBARI-19764.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/10309//console

This message is automatically generated.

> yarn.min.container.size is read incorrectly on first load of the Hive config page
> ---------------------------------------------------------------------------------
>
>                 Key: AMBARI-19764
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19764
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: 2.5.0
>            Reporter: Siddharth Seth
>            Assignee: Sumit Mohanty
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19764.patch
>
>
> The value is read in as 1024, even though min_container_size is 12GB on the cluster.
Impact: The values for minNodes, maxNodes, minConcurrency, maxConcurrency on the UI will be
incorrect. User selects an incorrect value and the cluster will not start.
> When various llap sliders are moved - the correct value of 12GB is read.
> The stack advisor code needs to be modified to take advantage of AMBARI-19701



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

Mime
View raw message