[
https://issues.apache.org/jira/browse/FLINK-9762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann resolved FLINK-9762.
----------------------------------
Resolution: Fixed
Fixed via
master:
6bdec86e31d82d7c38d2509a039a1a03ab9f246e
ec28f92ffd042308494d9661a38ab462738611aa
1.6.0:
fcd266fb439aa9288d6114d9bfb1e22011588d74
877cd7ef6e8a876a2a3579d0761bc2d160a4daf4
1.5.2:
221a2b3833634065c13492ce141a8ba674e630d6
b505e52e3e4e3824b0f75c977b090c6d6cd24c62
> 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: Oleksandr Nitavskyi
> 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)
