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-19578) Fix issues around modifying yarn min container size
Date Wed, 18 Jan 2017 00:57:27 GMT

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

Hadoop QA commented on AMBARI-19578:
------------------------------------

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

This message is automatically generated.

> Fix issues around modifying yarn min container size
> ---------------------------------------------------
>
>                 Key: AMBARI-19578
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19578
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: 2.5.0
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19578.patch
>
>
> * rename variables
> * do not over write yarn.nodemanager.resource.memory-mb when its not a fresh install
> * re-valuate how "ramPerContainer" is evaluated wrt yarn.scheduler.minimum-allocation-mb



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

Mime
View raw message