hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-3205) MR2 memory limits should be pmem, not vmem
Date Wed, 26 Oct 2011 23:59:32 GMT

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

Arun C Murthy updated MAPREDUCE-3205:
-------------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

I just committed this. Thanks Todd!

(PS: I fixed yarn-default.xml to have the right default for NM resources i.e. 8192 rather
than 8.)
                
> MR2 memory limits should be pmem, not vmem
> ------------------------------------------
>
>                 Key: MAPREDUCE-3205
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3205
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv2, nodemanager
>    Affects Versions: 0.23.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Blocker
>             Fix For: 0.23.0
>
>         Attachments: mr-3205.txt, mr-3205.txt, mr-3205.txt, mr-3205.txt, mr-3205.txt,
mr-3205.txt
>
>
> Currently, the memory resources requested for a container limit the amount of virtual
memory used by the container. On my test clusters, at least, Java processes take up nearly
twice as much vmem as pmem - a Java process running with -Xmx500m uses 935m of vmem and only
about 560m of pmem.
> This will force admins to either under-utilize available physical memory, or oversubscribe
it by configuring the available resources on a TT to be larger than the true amount of physical
RAM.
> Instead, I would propose that the resource limit apply to pmem, and allow the admin to
configure a "vmem overcommit ratio" which sets the vmem limit as a function of pmem limit.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message