[
https://issues.apache.org/jira/browse/AMBARI-19690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838299#comment-15838299
]
Hudson commented on AMBARI-19690:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6544 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6544/])
AMBARI-19690: NM Memory can end up being too high on nodes with many (jluniya:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6a8115572b328785532aed27c1dc44a1bac17a01])
* (edit) ambari-server/src/main/resources/stacks/stack_advisor.py
* (edit) ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/common/test_stack_advisor.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py
> NM Memory can end up being too high on nodes with many components
> -----------------------------------------------------------------
>
> Key: AMBARI-19690
> URL: https://issues.apache.org/jira/browse/AMBARI-19690
> Project: Ambari
> Issue Type: Improvement
> Reporter: Jayush Luniya
> Assignee: Jayush Luniya
> Attachments: AMBARI-19690.patch
>
>
> Ambari's Stack Advisor has a static method to compute OS/component overheads
> when computing the YARN config 'yarn.nodemanager.resource.memory-mb' for NM
> We should add validation to check if there are any NodeManagers that would
> have high memory usage based on co-located service components and report a
> warning.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
