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 "Darek Zbik (JIRA)" <ji...@apache.org> on 2006/04/04 22:27:43 UTC

[jira] Created: (HADOOP-119) ReduceTask.configure() is called twice

ReduceTask.configure() is called twice
--------------------------------------

         Key: HADOOP-119
         URL: http://issues.apache.org/jira/browse/HADOOP-119
     Project: Hadoop
        Type: Bug

  Components: mapred  
    Versions: 0.2    
    Reporter: Darek Zbik


ReduceTask.configure() is called twice for each created reduce task 
First call is done indirect from 
org.apache.hadoop.mapred.JobConf.newInstance()
called in ReduceTask.run(). Second call was in ReduceTask.run() just after creating a new instance. I suggest to remove the second call. For all new instances created in case of map task there are no directly xxx.configure();

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (HADOOP-119) ReduceTask.configure() is called twice

Posted by "Darek Zbik (JIRA)" <ji...@apache.org>.

     [ http://issues.apache.org/jira/browse/HADOOP-119?page=all ]

Darek Zbik updated HADOOP-119:
------------------------------

    Attachment: mapred.patch

One line patch tested in my codes.

> ReduceTask.configure() is called twice
> --------------------------------------
>
>          Key: HADOOP-119
>          URL: http://issues.apache.org/jira/browse/HADOOP-119
>      Project: Hadoop
>         Type: Bug

>   Components: mapred
>     Versions: 0.2
>     Reporter: Darek Zbik
>  Attachments: mapred.patch
>
> ReduceTask.configure() is called twice for each created reduce task 
> First call is done indirect from 
> org.apache.hadoop.mapred.JobConf.newInstance()
> called in ReduceTask.run(). Second call was in ReduceTask.run() just after creating a new instance. I suggest to remove the second call. For all new instances created in case of map task there are no directly xxx.configure();

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira