hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5881) Simplify configuration related to task-memory-monitoring and memory-based scheduling
Date Tue, 02 Jun 2009 11:48:07 GMT

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

Hemanth Yamijala commented on HADOOP-5881:

bq. It would be useful if the description of the above memory management parameters is added
in mapred-default.xml. Also mapred.tasktracker.vmem.reserved, mapred.task.default.maxvmem
and mapred.task.limit.maxvmem has to be removed from the xml.

+1 regarding documentation. I filed HADOOP-5957 to track this. But we are planning to introduce
backwards compatible options, so removing the configuration parameters from xml will not be
necessary. Please see HADOOP-5919.

> Simplify configuration related to task-memory-monitoring and memory-based scheduling
> ------------------------------------------------------------------------------------
>                 Key: HADOOP-5881
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5881
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Vinod K V
>            Assignee: Vinod K V
>             Fix For: 0.20.1
>         Attachments: HADOOP-5881-20090526-branch-20.1.txt, HADOOP-5881-20090526.1.txt
> The configuration we have now is pretty complicated. Besides everything else, the mechanism
of not specifying parameters separately for maps and reduces leads to problems like HADOOP-5811.
This JIRA should address simplifying things and at the same time solving these problems.

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

View raw message