You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2014/07/01 21:10:25 UTC

[jira] [Updated] (YARN-2224) Let TestContainersMonitor#testContainerKillOnMemoryOverflow work irrespective of the default settings

     [ https://issues.apache.org/jira/browse/YARN-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karthik Kambatla updated YARN-2224:
-----------------------------------

          Component/s: nodemanager
             Priority: Trivial  (was: Major)
     Target Version/s: 2.5.0
    Affects Version/s: 2.4.1
               Labels: newbie  (was: )
           Issue Type: Test  (was: Bug)

> Let TestContainersMonitor#testContainerKillOnMemoryOverflow work irrespective of the default settings
> -----------------------------------------------------------------------------------------------------
>
>                 Key: YARN-2224
>                 URL: https://issues.apache.org/jira/browse/YARN-2224
>             Project: Hadoop YARN
>          Issue Type: Test
>          Components: nodemanager
>    Affects Versions: 2.4.1
>            Reporter: Anubhav Dhoot
>            Assignee: Anubhav Dhoot
>            Priority: Trivial
>              Labels: newbie
>         Attachments: YARN-2224.patch
>
>
> If the default setting DEFAULT_NM_VMEM_CHECK_ENABLED is set to false the test will fail. Make the test pass not rely on the default settings but just let it verify that once the setting is turned on it actually does the memory check. See YARN-2225 which suggests we turn the default off.



--
This message was sent by Atlassian JIRA
(v6.2#6252)