[
https://issues.apache.org/jira/browse/FLINK-15447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17020757#comment-17020757
]
Rong Rong commented on FLINK-15447:
-----------------------------------
Thanks [~victor-wong] for the explanation. I think I understood the problem
much better now.
This is definitely a good question to address, one suggestion I have is: can we
put the goal / intent in the description. I think based on the discussion the
summary of this Jira can be :
Title: To improve utilization of the `java.io.tmpdir` for YARN module
Description: To achieve:
_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._
utilizing a fully flexible {{$PWD/tmp}} path is one of the solution but it also
run into issues that [~fly_in_gis] mentions as {{$PWD}} can be anything.
One thing I can think of is instead of letting user customize $PWD, we preset
the location of {{tmpdir}} to be relative to the YARN container dir root,
something like {{$CLUSTER_CONTAINER_DEFAULT_DIR_ROOT/$PWD_USER_DEFINE}}?? what
do you guys think?
> 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)
