hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5094) Disable mem monitoring by default in MiniMRYarnCluster
Date Fri, 22 Mar 2013 21:15:15 GMT

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

Siddharth Seth commented on MAPREDUCE-5094:
-------------------------------------------

https://issues.apache.org/jira/browse/YARN-449?focusedCommentId=13600632&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13600632
Could you mention the environment - is this a running cluster, a system using MiniMRYarnCluster,
etc ?

The vmem values can vary depending on the env (configure vMemToPMemRatio accordingly). compressedoops,
which I believe is enabled by default after a certain jvm version helps for 64bit JVMs.

I'm not super happy about disabling mem checks either, one option would be to disable the
VMEM check only. Downstream projects can enable these via the input conf if they really want
to.
Thoughts ?
                
> Disable mem monitoring by default in MiniMRYarnCluster
> ------------------------------------------------------
>
>                 Key: MAPREDUCE-5094
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5094
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>
> YARN-449. Some hbase tests were failing since containers were getting killed. 
> I believe these checks are disabled by default on the branch-1 MiniMRCluster.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message