hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8288) Remove references of mapred.child.ulimit etc. since they are not being used any more
Date Tue, 17 Apr 2012 17:45:24 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-8288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255761#comment-13255761

Hadoop QA commented on HADOOP-8288:

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

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

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/862//console

This message is automatically generated.
> Remove references of mapred.child.ulimit etc. since they are not being used any more
> ------------------------------------------------------------------------------------
>                 Key: HADOOP-8288
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8288
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.23.2
>            Reporter: Ravi Prakash
>            Assignee: Ravi Prakash
>         Attachments: HADOOP-8288.branch-0.23.patch
> Courtesy Philip Su, we found that (mapred.child.ulimit, mapreduce.map.ulimit, mapreduce.reduce.ulimit)
were not being used at all. The configuration exists but is never used. Its also mentioned
in mapred-default.xml and templates/../mapred-site.xml . Also the method getUlimitMemoryCommand
in Shell.java is now useless and can be removed.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message