[
https://issues.apache.org/jira/browse/FLINK-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16295317#comment-16295317
]
ASF GitHub Bot commented on FLINK-8279:
---------------------------------------
Github user EronWright commented on the issue:
https://github.com/apache/flink/pull/5176
@NicoK was this PR a response to an actual issue, and did it resolve it?
Do I understand correctly that this will cause the JM (blob server) to use
`taskmanager.tmp.dirs`? In addition to the TM blob cache, of course.
For the TM on YARN, is there really any effect? Looking at
MAPREDUCE-6472, seems the temp folder is already within the container. Can
you explain the actual effect? Thanks.
Note that the Mesos implementation doesn't actually configure
`taskmanager.tmp.dirs` at this time (though there's some dead code in TM). A
proper treatment of tmp folders on Mesos would involve the use of volumes.
> Use Mesos/YARN temp directories as fallback for BlobServer/Cache temp
> directories
> ---------------------------------------------------------------------------------
>
> Key: FLINK-8279
> URL: https://issues.apache.org/jira/browse/FLINK-8279
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Coordination, Network
> Affects Versions: 1.4.0
> Reporter: Nico Kruber
> Assignee: Nico Kruber
>
> Currently, the BLOB server and cache processes (temporarily) stash incoming
> files into their local file system in the directory given by the
> {{blob.storage.directory}} configuration property. If this property is not
> set or empty, it will fall back to {{java.io.tmpdir}}.
> Instead, in a Mesos/YARN environment, we could use the temporary directories
> they assigned to the Flink job which are not only the proper folder to use,
> but may also offer some more space.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
