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] [Updated] (MAPREDUCE-5094) Disable mem monitoring by default in MiniMRYarnCluster
Date Fri, 05 Apr 2013 00:18:16 GMT

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

Siddharth Seth updated MAPREDUCE-5094:

    Attachment: MAPREDUCE-5094.txt

Thanks for the quick review.

bq. Let's also disable pmem, no point in doing it for tests. If we want to validate the monitoring,
specific tests should do that.
Done. I don't have a strong preference on enabling / disabling this by default for the miniMRCluster.

bq. Rename mapreduce.minicluster.control-resource-monitoring to mapreduce.minicluster.enable-memory-monitoring?
I prefer the old name - since that applies to resoueces in general, and lets users control
what they want (instead of an enable all).
> 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
>    Affects Versions: 2.0.3-alpha
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>         Attachments: MAPREDUCE-5094.txt, MAPREDUCE-5094.txt
> 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

View raw message