[MAPREDUCE-6829] Add peak memory usage counter for each task

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-alpha4, 3.0.0
• Component/s: mrv2
• Hadoop Flags: Reviewed
• Assignee: Miklos Szegedi
• Reporter: Yufei Gu
• Created: 05/May/16 16:44
• Updated: 10/Jul/18 23:52
• Resolved: 26/Jan/17 19:14

Description

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 JIRA has the same feature from MAPREDUCE-4710. I file this new YARN JIRA since MAPREDUCE-4710 is pretty old one from MR 1.x era, it more or less assumes a branch-1 architecture, should be close at this point.

Issue Links

• is duplicated by: MAPREDUCE-6922 MapReduce jobs may fail during rolling upgrade due to MAPREDUCE-6829
• is duplicated by: MAPREDUCE-4710 Add peak memory usage counter for each task