You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "RocMarshal (Jira)" <ji...@apache.org> on 2020/05/05 10:02:00 UTC
[jira] [Updated] (FLINK-17472) StreamExecutionEnvironment and
ExecutionEnvironment in Yarn mode
[ https://issues.apache.org/jira/browse/FLINK-17472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
RocMarshal updated FLINK-17472:
-------------------------------
Attachment: demo.jpeg
> StreamExecutionEnvironment and ExecutionEnvironment in Yarn mode
> ----------------------------------------------------------------
>
> Key: FLINK-17472
> URL: https://issues.apache.org/jira/browse/FLINK-17472
> Project: Flink
> Issue Type: New Feature
> Components: Client / Job Submission, Deployment / YARN
> Affects Versions: 1.10.0
> Reporter: RocMarshal
> Priority: Major
>
> Expect to have such a mode of submission. Build the task directly in the Environment, and then submit the task in yarn mode. Just like RemoteStreamEnvironment, as long as you specify the parameters of the yarn cluster (host, port) or yarn configuration directory and HADOOP_USER_NAME, you can use the topology built by Env to submit the task .
> This submission method is best to minimize the transmission of resources required by yarn to start flink-jobmanager and taskmanagerrunner to ensure that flink can deploy tasks on the yarn cluster as quickly as possible.
> The simple demo as shown in the attachment .the parameter named 'env' containes all the operators about job ,like sources,maps,etc..
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)