[ https://issues.apache.org/jira/browse/FLINK-15447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17020889#comment-17020889 ]
Yang Wang commented on FLINK-15447: ----------------------------------- [~victor-wong] Usually, it could work. However, it is not guaranteed that we do not use other uses to write something into tmp directory. If the {{java.io.tmpdir}} is configurable, it makes many sense to me for the changes. For Yarn deployment, we will override it to {{$PWD/tmp}}. For other deployments, it will be the default value {{System.getProperty("java.io.tmpdir")}}. > 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)