Details
-
New Feature
-
Status: Resolved
-
Minor
-
Resolution: Duplicate
-
1.0.2
-
None
-
None
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.
Attachments
Attachments
Issue Links
- duplicates
-
MAPREDUCE-6829 Add peak memory usage counter for each task
- Resolved