[
https://issues.apache.org/jira/browse/HADOOP-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554412
]
Amareshwari Sri Ramadasu commented on HADOOP-2116:
--------------------------------------------------
bq. So we can replace configuration parameter "mapred.jar" by "job.local.dir",
which will point to the parent of "mapred.jar".
We cannot replace mapred.jar by job.local.dir because mapred.jar can be set and
get by setJar() and getJar() from client side. For example, launchWordCount in
TestMiniMRClassPath gives a different path for jar file.
To expose the shared directory through the configuration, We can set
localJobConf.set("job.local.dir", jobDir) in localizeJob()
and job Cache directory can be obtained as
File jobCacheDir = new File(new File(conf.get("job.local.dir")), "work");
> Job.local.dir to be exposed to tasks
> ------------------------------------
>
> Key: HADOOP-2116
> URL: https://issues.apache.org/jira/browse/HADOOP-2116
> Project: Hadoop
> Issue Type: Improvement
> Components: mapred
> Affects Versions: 0.14.3
> Environment: All
> Reporter: Milind Bhandarkar
> Fix For: 0.16.0
>
>
> Currently, since all task cwds are created under a jobcache directory, users
> that need a job-specific shared directory for use as scratch space, create
> ../work. This is hacky, and will break when HADOOP-2115 is addressed. For
> such jobs, hadoop mapred should expose job.local.dir via localized
> configuration.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
