[
https://issues.apache.org/jira/browse/HADOOP-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616364#action_12616364
]
Hadoop QA commented on HADOOP-3131:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12386638/HADOOP-3131-v5.patch
against trunk revision 679202.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 8 new or modified tests.
+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 failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2933/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2933/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2933/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2933/console
This message is automatically generated.
> enabling BLOCK compression for map outputs breaks the reduce progress counters
> ------------------------------------------------------------------------------
>
> Key: HADOOP-3131
> URL: https://issues.apache.org/jira/browse/HADOOP-3131
> Project: Hadoop Core
> Issue Type: Bug
> Affects Versions: 0.17.0, 0.17.1, 0.17.2, 0.18.0, 0.19.0
> Reporter: Colin Evans
> Assignee: Matei Zaharia
> Fix For: 0.19.0
>
> Attachments: HADOOP-3131-v2.patch, HADOOP-3131-v3.patch,
> HADOOP-3131-v4.patch, HADOOP-3131-v5.patch, merge-progress-trunk.patch,
> merge-progress.patch, Picture 1.png
>
>
> Enabling map output compression and setting the compression type to BLOCK
> causes the progress counters during the reduce to go crazy and report
> progress counts over 100%.
> This is problematic for speculative execution because it thinks the tasks are
> doing fine.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
