Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <577283587.1213207847080.JavaMail.jira@brutus>
Date: Wed, 11 Jun 2008 11:10:47 -0700 (PDT)
From: "Matei Zaharia (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3131) enabling BLOCK compression for map
 outputs breaks the reduce progress counters
In-Reply-To: <61007758.1206753744262.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604294#action_12604294 ] 

Matei Zaharia commented on HADOOP-3131:
---------------------------------------

Looking at the patch submitted for HADOOP-2095, it seems that it has the same problem (by doing totalBytesProcessed += (key.getLength()-key.getPosition()) + 
 (value.getLength()-value.getPosition())). I can submit a separate patch against 18 to fix that, but it would also be good to place this in 17 because 18 is not getting released for a while.


> 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.18.0
>            Reporter: Colin Evans
>         Attachments: 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 message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.