[
https://issues.apache.org/jira/browse/FLINK-15447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17063064#comment-17063064
]
Victor Wong commented on FLINK-15447:
-------------------------------------
Currently, we can solve this issue through "env.java.opts:
-Djava.io.tmpdir=./tmp", closing this issue now.
> To improve utilization of the `java.io.tmpdir` for YARN module
> --------------------------------------------------------------
>
> Key: FLINK-15447
> URL: https://issues.apache.org/jira/browse/FLINK-15447
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
> Affects Versions: 1.9.1
> Reporter: Victor Wong
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *#Background*
> Currently, when running Flink on Yarn, the "java.io.tmpdir" property is set
> to the default value, which is "/tmp".
> Sometimes we ran into exceptions caused by a full "/tmp" directory, which
> would not be cleaned automatically after applications finished.
>
> #*Goal*
> quoted from: [HADOOP-2735|https://issues.apache.org/jira/browse/HADOOP-2735]
> _1) Tasks can utilize all disks when using tmp_
> _2) Any undeleted tmp files will be deleted by the tasktracker when
> task(job?) is done._
>
> #*Suggestion*
> I think we can set "java.io.tmpdir" to "{{{{PWD}}}}/tmp" directory, or
> something similar. "{{{{PWD}}}}" will be replaced with the true working
> directory of JM/TM by Yarn, which will be cleaned automatically.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
