You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "TisonKun (JIRA)" <ji...@apache.org> on 2019/01/04 02:59:00 UTC
[jira] [Commented] (FLINK-11263) yarn session script doesn't boot
up task managers
[ https://issues.apache.org/jira/browse/FLINK-11263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733749#comment-16733749 ]
TisonKun commented on FLINK-11263:
----------------------------------
[~hongtao12310] It's an unimplemented future, see also FLINK-11078. I'm working on it and what you see for now is how Flink(after FLIP-6) works currently.
> yarn session script doesn't boot up task managers
> -------------------------------------------------
>
> Key: FLINK-11263
> URL: https://issues.apache.org/jira/browse/FLINK-11263
> Project: Flink
> Issue Type: Bug
> Components: Cluster Management
> Affects Versions: 1.6.3
> Environment: Flink 1.6.3
> Hadoop 2.7.5
> Reporter: Hongtao Zhang
> Priority: Critical
>
> {{./bin/yarn-session.sh -n 4 -jm 1024m -tm 4096m}}
> {{I want to boot up a Yarn Session Cluster use the command above}}
> {{but Flink doesn't create the task executors but only the applicationMaster(YarnSessionClusterEntryPoint)}}
>
> {{the Task Executors will be created when a job was submitted.}}
>
> {{the point is that Yarn ResourceManager doesn't know how many task executors should be created because the -n option was not accept by ResourceMananger}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)