[
https://issues.apache.org/jira/browse/HADOOP-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated HADOOP-2116:
----------------------------------
Status: Open (was: Patch Available)
This patch sets a system property 'job.local.dir', I'm assuming that it is
inherited by the children?
{noformat}
+ System.setProperty("job.local.dir", workDir.toString());
{noformat}
Even so, I think we should set a property in the JobConf to be consistent.
----
Overall, I'm a little concerned that this is quite late (w.r.t 0.16.0) to be
getting this in. I spoke to Milind and he is happy with the HADOOP-2570 (the
symlink to ../work) - especially given the number of changes we need to make
where we use something.getParent().{}. Hence I propose we push this to 0.17.0
and also make it a bigger change incorporating wider changes to the task's
local directories proposed by Owen. Thoughts?
> 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
> Assignee: Amareshwari Sri Ramadasu
> Fix For: 0.16.0
>
> Attachments: patch-2116.txt, patch-2116.txt, patch-2116.txt,
> patch-2116.txt
>
>
> 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.
