[
https://issues.apache.org/jira/browse/MAPREDUCE-5367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720939#comment-13720939
]
Sandy Ryza commented on MAPREDUCE-5367:
---------------------------------------
I don't think the problem exists in trunk. getLocalTaskDir includes the job ID
in the path, so there shouldn't be collisions. The other place that
localRunner/ is used is for writing the job conf, which includes the job ID in
its name. So that also should not be a problem. Though thinking about it now,
it might make sense to change it as well for consistency?
> Local jobs all use same local working directory
> -----------------------------------------------
>
> Key: MAPREDUCE-5367
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5367
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Affects Versions: 1.2.0
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Attachments: MAPREDUCE-5367-b1.patch
>
>
> This means that local jobs, even in different JVMs, can't run concurrently
> because they might delete each other's files during work directory setup.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
