[
https://issues.apache.org/jira/browse/MAPREDUCE-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15610878#comment-15610878
]
Gera Shegalov commented on MAPREDUCE-6793:
------------------------------------------
[~rohithsharma], this 100 in code is irrelevant because of the definition in
mapred-default.xml that is inside mapreduce jar. We should include this kind of
unit test in the patch, maybe in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/test/java/org/apache/hadoop/mapreduce/task/reduce/TestMergeManager.java
{code}
@Test
public void testDefaultIoSortFactor() {
final JobConf jobConf = new JobConf();
assertEquals(10, jobConf.getInt(MRJobConfig.IO_SORT_FACTOR, 100));
}
{code}
to demonstrate it.
> io.sort.factor code default and mapred-default.xml values inconsistent
> ----------------------------------------------------------------------
>
> Key: MAPREDUCE-6793
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6793
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: task
> Affects Versions: 2.6.5, 3.0.0-alpha1
> Reporter: Gera Shegalov
> Assignee: Prabhu Joseph
> Priority: Trivial
> Labels: noob
> Attachments: 0001-MAPREDUCE-6793.patch
>
>
> The actual default value in mapred-default.xml:
> {code}
> <property>
> <name>mapreduce.task.io.sort.factor</name>
> <value>10</value>
> <description>The number of streams to merge at once while sorting
> files. This determines the number of open file handles.</description>
> </property>
> {code}
> However, MapTask and MergeManagerImpl, are coded with:
> {code}
> int mergeFactor = job.getInt(JobContext.IO_SORT_FACTOR, 100);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
