[ https://issues.apache.org/jira/browse/MAPREDUCE-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470964#comment-13470964 ]
Harsh J commented on MAPREDUCE-4710: ------------------------------------ Cindy, Thanks! This would come useful. The branch-1 is a maintenance branch that should not receive new features first and diverge from trunk. Please also provide a trunk patch that can go in first, so we maintain feature parity. Or if trunk does not require this, please explain. > Add peak memory usage counter for each task > ------------------------------------------- > > Key: MAPREDUCE-4710 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4710 > Project: Hadoop Map/Reduce > Issue Type: New Feature > Components: task > Affects Versions: 1.0.2 > Reporter: Cindy Li > Priority: Minor > Labels: patch > Attachments: mapreduce-4710.patch > > > Each task has counters PHYSICAL_MEMORY_BYTES and VIRTUAL_MEMORY_BYTES, which > are snapshots of memory usage of that task. They are not sufficient for users > to understand peak memory usage by that task, e.g. in order to diagnose task > failures, tune job parameters or change application design. This new feature > will add two more counters for each task: PHYSICAL_MEMORY_BYTES_MAX and > VIRTUAL_MEMORY_BYTES_MAX. -- 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