[
https://issues.apache.org/jira/browse/FLINK-9762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16541869#comment-16541869
]
ASF GitHub Bot commented on FLINK-9762:
---------------------------------------
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/6284#discussion_r202075077
--- Diff:
flink-core/src/main/java/org/apache/flink/configuration/CoreOptions.java ---
@@ -181,12 +181,17 @@
* The config parameter defining the directories for temporary files,
separated by
* ",", "|", or the system's {@link java.io.File#pathSeparator}.
*/
- @Documentation.OverrideDefault("System.getProperty(\"java.io.tmpdir\")")
+ @Documentation.OverrideDefault("'LOCAL_DIRS' on Yarn and
'_FLINK_TMP_DIR' on Mesos.")
--- End diff --
We should also keep saying that in the standalone mode we use
`System.getProperty("java.io.tmpdir")`
> CoreOptions.TMP_DIRS wrongly managed on Yarn
> --------------------------------------------
>
> Key: FLINK-9762
> URL: https://issues.apache.org/jira/browse/FLINK-9762
> Project: Flink
> Issue Type: Bug
> Components: YARN
> Affects Versions: 1.5.0
> Reporter: Oleksandr Nitavskyi
> Assignee: vinoyang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.2, 1.6.0
>
>
> The issue on Yarn is that it is impossible to have different LOCAL_DIRS on
> JobManager and TaskManager, despite LOCAL_DIRS value depends on the container.
> The issue is that CoreOptions.TMP_DIRS is configured to the default value
> during JobManager initialization and added to the configuration object. When
> TaskManager is launched the appropriate configuration object is cloned with
> LOCAL_DIRS which makes sense only for Job Manager container. When YARN
> container with TaskManager from his point of view CoreOptions.TMP_DIRS is
> always equal either to path in flink.yml or to the or to the LOCAL_DIRS of
> Job Manager (default behaviour). Is TaskManager’s container do not have an
> access to another folders, that folders allocated by YARN TaskManager cannot
> be started.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
