ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jayush Luniya (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-19690) NM Memory can end up being too high on nodes with many components
Date Wed, 25 Jan 2017 18:24:27 GMT

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

Jayush Luniya commented on AMBARI-19690:
----------------------------------------

Trunk
commit 6a8115572b328785532aed27c1dc44a1bac17a01
Author: Jayush Luniya <jluniya@hortonworks.com>
Date:   Wed Jan 25 09:40:56 2017 -0800

    AMBARI-19690: NM Memory can end up being too high on nodes with many components (jluniya)

branch-2.5
commit b84a32b374adbbb97ee0141d4fd8deb3ec2fbcee
Author: Jayush Luniya <jluniya@hortonworks.com>
Date:   Wed Jan 25 10:21:57 2017 -0800

    AMBARI-19690: NM Memory can end up being too high on nodes with many components (jluniya)

> 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)

Mime
View raw message