You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Oleksandr Nitavskyi (JIRA)" <ji...@apache.org> on 2018/07/05 10:52:00 UTC
[jira] [Created] (FLINK-9762) CoreOptions.TMP_DIRS wrongly managed
on Yarn
Oleksandr Nitavskyi created FLINK-9762:
------------------------------------------
Summary: 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
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)