[
https://issues.apache.org/jira/browse/FLINK-15447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17018462#comment-17018462
]
Victor Wong commented on FLINK-15447:
-------------------------------------
[~rongr] Thanks for your reply!
_Could you elaborate what does it mean by Flink-YARN default the value to /tmp?
I am guessing you mean JVM default the value to /tmp ?
_
---
Yes, I mean that Flink-YARN is using the default value of JVM, which is "/tmp".
_So far the only place I can see in flink yarn code utilizing this key is:
https://github.com/apache/flink/blob/release-1.10/flink-yarn/src/main/java/org/apache/flink/yarn/cli/FlinkYarnSessionCli.java#L899
_
---
The third-party dependencies might utilize this key as well, as [~lzljs3620320]
mentioned.
My intention is similar to how [~xymaqingxiang] mentioned that setting the
value to a tmp directory under the working directory of Yarn container.
> Change "java.io.tmpdir" of JM/TM on Yarn to "{{PWD}}/tmp"
> -----------------------------------------------------------
>
> 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
>
> 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.
> 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)
