[
https://issues.apache.org/jira/browse/HADOOP-3332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595913#action_12595913
]
Devaraj Das commented on HADOOP-3332:
-------------------------------------
Arun, actually there was a call to currentTimeMillis already. I moved it up so
that it can be reused for logging also. From the patch, this is the place where
currentTime is removed from...
@@ -1098,7 +1123,7 @@
Iterator<MapOutputLocation> locIt = knownOutputs.iterator();
- currentTime = System.currentTimeMillis();
+
while (locIt.hasNext()) {
MapOutputLocation loc = locIt.next();
@@ -1112,8 +1137,12 @@
> 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
> Reporter: Runping Qi
> Assignee: Devaraj Das
> Priority: Critical
> 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.
