You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2009/05/27 01:19:45 UTC
[jira] Reopened: (HADOOP-5881) Simplify configuration related to
task-memory-monitoring and memory-based scheduling
[ https://issues.apache.org/jira/browse/HADOOP-5881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen O'Malley reopened HADOOP-5881:
-----------------------------------
I'm concerned that this went in without an opportunity for review. The patch was uploaded at 5:49am and committed at 6:36am.
I'm also concerned that this incompatibly changes the config variables in the 0.20 branch. What is the rationale for pushing these configuration changes back to 0.20? If they are required, they need a compatability story.
> 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.