[ https://issues.apache.org/jira/browse/FLINK-15447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17028644#comment-17028644 ]
Victor Wong commented on FLINK-15447: ------------------------------------- [~trohrmann], thanks for your attention. _I am wondering whether you would like to configure the system property {{java.io.tmpdir}} to point towards {{./tmp}} or to only change Flink's temp directories._ _---_ The former, configure the system property java.io.tmpdir. _If not, then we would need to adapt the java command which starts the Flink processes._ _---_ I think this is the best choice, which has _the benefit that libraries, relying on {{java.io.tmpdir}}, will not write their temporary data to {{/tmp}}, too._ > 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 > > *#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)