[
https://issues.apache.org/jira/browse/TEZ-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14737428#comment-14737428
]
Jonathan Eagles commented on TEZ-2787:
--------------------------------------
With the patch above here is the new addition to the DAGAppMaster java process
being run.
{code}
-Djava.io.tmpdir=/Users/jeagles/run/tmp/nm-local-dir/usercache/jeagles/appcache/application_1441825297926_0002/container_1441825297926_0002_01_000001/tmp
{code}
This is currently used for Jetty in the AM and is not too large.
{code}
du -sch
/Users/jeagles/run/tmp/nm-local-dir/usercache/jeagles/appcache/application_1441825297926_0002/container_1441825297926_0002_01_000001/tmp
404K
/Users/jeagles/run/tmp/nm-local-dir/usercache/jeagles/appcache/application_1441825297926_0002/container_1441825297926_0002_01_000001/tmp
{code}
This is going to do a better job of cleaning up temp files with this setup and
be less susceptible to tmpwatch process cleaning up unarchived files with old
timestamps in the /tmp dir.
> Tez AM should have java.io.tmpdir=./tmp to be consistent with tasks
> -------------------------------------------------------------------
>
> Key: TEZ-2787
> URL: https://issues.apache.org/jira/browse/TEZ-2787
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Jason Lowe
> Attachments: TEZ-2787.1.patch
>
>
> TezRuntimeChildJVM ensures that tasks are launched with
> -Djava.io.tmpdir=./tmp, but there's no corresponding code to ensure the Tez
> AM also has a similar tmpdir setting. The client should setup the AM launch
> context to have -Djava.io.tmpdir=./tmp to be consistent with the tasks and to
> prevent accidental leaking of files in /tmp by the Tez AM if it crashes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
