[
https://issues.apache.org/jira/browse/HADOOP-3332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595447#action_12595447
]
Hadoop QA commented on HADOOP-3332:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12381688/3332.patch
against trunk revision 654315.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2430/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2430/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2430/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2430/console
This message is automatically generated.
> 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.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.
