hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5652) Reduce does not respect in-memory segment memory limit when number of on disk segments == io.sort.factor
Date Fri, 10 Apr 2009 05:25:12 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Douglas updated HADOOP-5652:
----------------------------------

    Attachment: 5652-1.patch

Better fix; should merge in-memory segments with the smallest on-disk segment

> Reduce does not respect in-memory segment memory limit when number of on disk segments
== io.sort.factor
> --------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-5652
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5652
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.20.0
>            Reporter: Chris Douglas
>            Priority: Minor
>         Attachments: 5652-0.patch, 5652-1.patch
>
>
> If the number of on-disk segments is exactly {{io.sort.factor}}, then map output segments
may be left in memory for the reduce contrary to the specification in {{mapred.job.reduce.input.buffer.percent}}.

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


Mime
View raw message