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 "Hudson (JIRA)" <ji...@apache.org> on 2014/07/11 00:24:04 UTC

[jira] [Commented] (YARN-2224) Explicitly enable vmem check in TestContainersMonitor#testContainerKillOnMemoryOverflow

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

Hudson commented on YARN-2224:
------------------------------

FAILURE: Integrated in Hadoop-trunk-Commit #5862 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/5862/])
YARN-2224. Fix CHANGES.txt. This was committed as YARN-2204 before. (kasha: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1609582)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt


> Explicitly enable vmem check in TestContainersMonitor#testContainerKillOnMemoryOverflow
> ---------------------------------------------------------------------------------------
>
>                 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
>             Fix For: 2.5.0
>
>         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)