hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4710) Add peak memory usage counter for each task
Date Tue, 31 Dec 2013 01:44:50 GMT

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

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

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12620887/mapreduce4710-v6.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
1.3.9) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient hadoop-tools/hadoop-rumen.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4291//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/4291//console

This message is 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, trunk
>            Reporter: Cindy Li
>            Assignee: Cindy Li
>            Priority: Minor
>              Labels: patch
>             Fix For: trunk
>
>         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.1.5#6160)

Mime
View raw message