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] Commented: (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 19:44:14 GMT

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

Chris Douglas commented on HADOOP-5652:
---------------------------------------

{noformat}
Test org.apache.hadoop.hdfs.server.namenode.TestReplicationPolicy FAILED
Test org.apache.hadoop.mapred.TestMRServerPorts FAILED
Test org.apache.hadoop.mapred.TestQueueCapacities FAILED
{noformat}

None of the test failures were caused by the patch.

> 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
>            Assignee: Chris Douglas
>            Priority: Minor
>             Fix For: 0.21.0
>
>         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