[
https://issues.apache.org/jira/browse/TEZ-3008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohini Palaniswamy resolved TEZ-3008.
-------------------------------------
Resolution: Duplicate
Sorry. My bad. I did not link the jiras with the original Oozie issue which
brought out the problem and I thought I had not filed it yet. I did search but
I did not get it right.
> AM java.io.tmpdir should be set to $PWD/tmp
> -------------------------------------------
>
> Key: TEZ-3008
> URL: https://issues.apache.org/jira/browse/TEZ-3008
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Rohini Palaniswamy
> Labels: newbie
>
> For tasks it is already done by TezRuntimeChildJVM
> {code}
> Path childTmpDir = new Path(Environment.PWD.$(),
> YarnConfiguration.DEFAULT_CONTAINER_TEMP_DIR);
> vargs.add("-Djava.io.tmpdir=" + childTmpDir);
> {code}
> Need to do this in AM as well. Mapreduce has uber mode which usually causes
> more problem (MAPREDUCE-6576), when user code writes to java.io.tmpdir as it
> defaults to /tmp in AM and fills up disk space on cluster nodes. Even though
> there is no uber mode with Tez AM that can cause problem, there is still the
> chance that the output committer code of users which run in AM can write
> something to java.io.tmpdir.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
