flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-9762) CoreOptions.TMP_DIRS wrongly managed on Yarn
Date Tue, 10 Jul 2018 11:41:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-9762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538442#comment-16538442

ASF GitHub Bot commented on FLINK-9762:

Github user yanghua commented on the issue:

    find related test error, please recheck~

> 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
> 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

View raw message