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-870) Clean up the job Retire code
Date Mon, 17 Aug 2009 10:44:14 GMT

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

Hadoop QA commented on MAPREDUCE-870:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision 804865.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 7 new or modified tests.

    -1 javadoc.  The javadoc tool appears to have generated 1 warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit

    -1 core tests.  The patch failed core unit tests.

    -1 contrib tests.  The patch failed contrib unit tests.

Test results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/484/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/484/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/484/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/484/console

This message is automatically generated.

> Clean up the job Retire code
> ----------------------------
>                 Key: MAPREDUCE-870
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-870
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>            Reporter: Sharad Agarwal
>            Assignee: Sharad Agarwal
>         Attachments: 870_v1.patch, 870_v2.patch
> Currently completed job's full data structures are kept in memory based on mapred.jobtracker.completeuserjobs.maximum,
mapred.jobtracker.retirejob.interval.min, mapred.jobtracker.retirejob.interval and mapred.jobtracker.retirejob.check
settings. These controls are not much useful now since MAPREDUCE-817 introduced a cache for
keeping just the very basic info of the completed job. These settings should be removed and
the job should be purged as soon as the history files are available in HDFS. 
> Going forward, clients can read the history files if they need to drill down into more
information (MAPREDUCE-864).

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message