Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <931339607.1212465525131.JavaMail.jira@brutus>
Date: Mon, 2 Jun 2008 20:58:45 -0700 (PDT)
From: "Chris Douglas (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-3475) MapOutputBuffer allocates 4x as much
 space to record capacity as intended
In-Reply-To: <71408749.1212187245146.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-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Douglas updated HADOOP-3475:
----------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]
          Status: Resolved  (was: Patch Available)

I just committed this.

> MapOutputBuffer allocates 4x as much space to record capacity as intended
> -------------------------------------------------------------------------
>
>                 Key: HADOOP-3475
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3475
>             Project: Hadoop Core
>          Issue Type: Bug
>    Affects Versions: 0.17.0
>            Reporter: Chris Douglas
>            Assignee: Chris Douglas
>             Fix For: 0.18.0
>
>         Attachments: 3475-1.patch, 3475-2.patch
>
>
> When setting up its accounting tables, MapTask.MapOutputBuffer calculates the size of each of its buffers as:
> {noformat}
> Where #total_bytes is $io.sort.mb * 2^20 and #accounting_bytes is $io.sort.record.percent * #total_bytes
> kvbuffer: #total_bytes - #accounting_bytes
> kvoffsets: 1/4 of #accounting_bytes
> kvindices: 3/4 of #accounting_bytes
> {noformat}
> kvoffsets and kvindices are ints, not bytes; the size of both arrays is incorrectly calculated.

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