[
https://issues.apache.org/jira/browse/FLINK-15447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17018759#comment-17018759
]
Yang Wang commented on FLINK-15447:
-----------------------------------
Even Flink does not write too much things, the users codes and third-party
dependencies may do this. So in general, i think it is a valid fix. I just have
one more concern.
Usually, the permission of /tmp directory in most OS is 777. So all the users
and processes could write some thing into the tmp directory. If we change it
the {{PWD}} which is the workDir of the Yarn container, the permission will
depend on the Yarn configuration. It could be user yarn, the proxy user, or the
submission user. The changes make sense for most cases. However, i'm not sure
it works for all cases.
How do we handle this situation? Set the permission to 777 or something else?
> 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)
