[jira] [Commented] (MAPREDUCE-4710) Add peak memory usage counter for each task

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629977#comment-14629977 ] 

Hadoop QA commented on MAPREDUCE-4710:
--------------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch |   0m  0s | The patch command could not apply the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12620887/mapreduce4710-v6.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 1ba2986 |
| Console output | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5891/console |


This message was automatically generated.

> 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
>            Assignee: Cindy Li
>            Priority: Minor
>         Attachments: MAPREDUCE-4710-trunk.patch, mapreduce-4710-v1.0.2.patch, mapreduce-4710.patch, mapreduce4710-v3.patch, mapreduce4710-v6.patch, mapreduce4710.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 was sent by Atlassian JIRA
(v6.3.4#6332)