You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Yang Hao (JIRA)" <ji...@apache.org> on 2014/06/21 10:39:24 UTC
[jira] [Updated] (MAPREDUCE-2398) MRBench: setting the baseDir
parameter has no effect
[ https://issues.apache.org/jira/browse/MAPREDUCE-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yang Hao updated MAPREDUCE-2398:
--------------------------------
Tags: MRBench
Fix Version/s: (was: 0.22.1)
2.5.0
1.3.0
Assignee: Yang Hao
Target Version/s: 2.3.0, 2.5.0
Affects Version/s: 2.5.0
2.4.0
2.3.0
Status: In Progress (was: Patch Available)
This problem still exists in the version Hadoop-2.3.0, so please fix it in the java "org.apache.hadoop.mapred.MRBench".Sometimes we don't have the permission to operate all the HDFS file, so we have to change the BASE_DIR , and the INPUT_DIR and OUTPUT_DIR should be updated when BASE_DIR is set. Only two extra lines be put into the java source code can solve the bug
> MRBench: setting the baseDir parameter has no effect
> ----------------------------------------------------
>
> Key: MAPREDUCE-2398
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2398
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: benchmarks
> Affects Versions: 2.3.0, 0.22.0, 0.20.2, 2.4.0, 2.5.0
> Reporter: Michael Noll
> Assignee: Yang Hao
> Priority: Minor
> Fix For: 1.3.0, 2.5.0
>
> Attachments: MAPREDUCE-2398-trunk.patch, MAPREDUCE-2398_0.20.2.patch, MAPREDUCE-2398_v2-0.20.203.0.patch, MAPREDUCE-2398_v2-trunk.patch
>
>
> The optional {{-baseDir}} parameter lets user specify the base DFS path for output/input of MRBench.
> However, the two private variables {{INPUT_DIR}} and {{OUTPUT_DIR}} (MRBench.java) are not updated in the case that the default value of {{-baseDir}} is actually overwritten by the user. Hence any input and output is always written to the default locations ({{/benchmarks/MRBench/...}}), even though the user-supplied location for {{-baseDir}} is created (and eventually deleted again) on HDFS.
> The bug affects at least Hadoop 0.20.2 and the current trunk (r1082703) as of March 21, 2011.
--
This message was sent by Atlassian JIRA
(v6.2#6252)