[
https://issues.apache.org/jira/browse/MAPREDUCE-5367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699450#comment-13699450
]
Ben Podgursky commented on MAPREDUCE-5367:
------------------------------------------
For what it's worth, our current hacky workaround to this bug is prefixing the
working directory with a UUID in LocalJobRunner:
String tmpDir = jobDir + "/" + id + "-"+ UUID.randomUUID();
this.localJobDir = localFs.makeQualified(conf.getLocalPath(tmpDir));
and deleting it on job cleanup:
localFs.delete(localJobDir, true);
But I'm sure there's a cleaner way to scope the paths.
> 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
>
> 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
