[ 
https://issues.apache.org/jira/browse/FLINK-15447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009578#comment-17009578
 ] 

xymaqingxiang commented on FLINK-15447:
---------------------------------------

+1

We also set "java.io.tmpdir" to "{{{{PWD}}}}/tmp" directory internally.

 
{code:java}
// when encapsulating the StartCommandValues for JM/TM
Path tmpDir = new Path(ApplicationConstants.Environment.PWD.$$(), 
YarnConfiguration.DEFAULT_CONTAINER_TEMP_DIR);
javaOpts = "-Djava.io.tmpdir=" + tmpDir.getPath();
startCommandValues.put("jvmopts", javaOpts);
{code}

> 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)

Reply via email to