hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3332) improving the logging during shuffling
Date Tue, 13 May 2008 22:33:55 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-3332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Owen O'Malley updated HADOOP-3332:
----------------------------------

    Affects Version/s:     (was: 0.17.0)
                       0.18.0
        Fix Version/s:     (was: 0.17.0)
                       0.18.0

This was caused by HADOOP-3297, which was only committed to 0.18. The confusion happened because
Runping was running with it applied to 0.17.

> improving the logging during shuffling
> --------------------------------------
>
>                 Key: HADOOP-3332
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3332
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>    Affects Versions: 0.18.0
>            Reporter: Runping Qi
>            Assignee: Devaraj Das
>            Priority: Blocker
>             Fix For: 0.18.0
>
>         Attachments: 3332.branch17.patch, 3332.patch, 3332.patch
>
>
> Below is an excerpt from the log file of a reducer. 
> A same set of of messages about fetching schedule is logged every second. 
> Yet, the critical information --- which hosts were slow --- was not there. 
>   
> 2008-05-01 00:33:13,215 INFO org.apache.hadoop.mapred.ReduceTask: task_200804302255_0002_r_000720_0
Need another 3 map output(s) where 1 is already in progress 
> 2008-05-01 00:33:14,216 INFO org.apache.hadoop.mapred.ReduceTask: task_200804302255_0002_r_000720_0:
Got 0 new map-outputs & 0 obsolete map-outputs from tasktracker and 0 map-outputs from
previous failures 
> 2008-05-01 00:33:14,216 INFO org.apache.hadoop.mapred.ReduceTask: task_200804302255_0002_r_000720_0
Got 2 known map output location(s); scheduling... 
> 2008-05-01 00:33:14,216 INFO org.apache.hadoop.mapred.ReduceTask: task_200804302255_0002_r_000720_0
Scheduled 0 of 2 known outputs (2 slow hosts and 0 dup hosts) 
> 2008-05-01 00:33:14,216 INFO org.apache.hadoop.mapred.ReduceTask: task_200804302255_0002_r_000720_0
Need another 3 map output(s) where 1 is already in progress 
> 2008-05-01 00:33:15,217 INFO org.apache.hadoop.mapred.ReduceTask: task_200804302255_0002_r_000720_0:
Got 0 new map-outputs & 0 obsolete map-outputs from tasktracker and 0 map-outputs from
previous failures 
> 2008-05-01 00:33:15,217 INFO org.apache.hadoop.mapred.ReduceTask: task_200804302255_0002_r_000720_0
Got 2 known map output location(s); scheduling... 
> 2008-05-01 00:33:15,217 INFO org.apache.hadoop.mapred.ReduceTask: task_200804302255_0002_r_000720_0
Scheduled 0 of 2 known outputs (2 slow hosts and 0 dup hosts) 
> 2008-05-01 00:33:15,217 INFO org.apache.hadoop.mapred.ReduceTask: task_200804302255_0002_r_000720_0
Need another 3 map output(s) where 1 is already in progress 
> 2008-05-01 00:33:16,218 INFO org.apache.hadoop.mapred.ReduceTask: task_200804302255_0002_r_000720_0:
Got 0 new map-outputs & 0 obsolete map-outputs from tasktracker and 0 map-outputs from
previous failures 

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


Mime
View raw message