ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-19578) Fix issues around modifying yarn min container size
Date Wed, 18 Jan 2017 08:18:26 GMT

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

Hudson commented on AMBARI-19578:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6475 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6475/])
AMBARI-19578. Fix issues around modifying yarn min container size (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e0d78edb94cbbfe56b075487d241143f337a0a87])
* (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/common/test_stack_advisor.py
* (edit) ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py
* (edit) ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py


> 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